Use when a Spark branch or pull request needs final diff hygiene, validation selection, commit scope, remote topology, and readiness checked before publication.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Treat repository and remote state as evidence. The upstream Session retains publication authority.
CONTRIBUTING.md, the validation matrix, PR template, and applicable subtree instructions.Never push, force-push, create, ready, merge, or close a PR. Never claim a check passed from an old SHA. Reject when intended commit scope is ambiguous or required evidence is absent.
Return diffScope, commands, acceptanceEvidence, remoteState, pending, verdict, and blockingReasons.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when Spark engineering knowledge must be placed, deduplicated, migrated, or validated across AGENTS, Notes, Roles, Skills, and Workflows.
The English summary is being prepared. Showing the original description.
Use when adding or updating Spark AI provider models or their compact and preflight metrics, especially baidu-oneapi, Grok, Claude, GPT, DeepSeek, OneAPI, context windows, output budgets, prices, thinking maps, or transports.
The English summary is being prepared. Showing the original description.
Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.
The English summary is being prepared. Showing the original description.
Use when a Spark implementation needs an evidence-based review for correctness, ownership, compatibility, failure handling, maintainability, and unnecessary complexity.
The English summary is being prepared. Showing the original description.
Use when designing a Spark feature or writing or materially revising a design proposal that needs repository-first research, user input on unresolved key choices, and an owner-aligned implementation plan before code changes.
The English summary is being prepared. Showing the original description.
Use when a working Spark implementation should be simplified without changing its observed behavior, ownership, compatibility, or public contract.
The English summary is being prepared. Showing the original description.