Post-change checks before handing off. Works out which checks apply from the files changed (directory AGENTS.md Checks sections and matching .agents/rules), runs or verifies each, and reports pass/fail/skipped. Use before saying work is done, before pushing, or when asked to audit or verify a change.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Delegate to the auditor subagent when it is available, passing the base branch
(default origin/main), so command output stays out of your context. Otherwise
follow these steps yourself.
base=$(git merge-base HEAD origin/main)
{ git diff --name-only "$base"; git ls-files --others --exclude-standard; } | sort -u
For every changed file:
AGENTS.md from the file's directory up to the repo
root: take its ## Checks section, and the root guide's "Before handing off"..agents/rules/ whose paths: globs match the file, plus
rules with no paths:. Every bullet is a requirement to verify against the diff;
a Check: line is a step to run.| Changed | Check |
|---|---|
| Any | just check |
| Rust in a package | cargo test -p <package> (SQLX_OFFLINE unset), cargo fmt --all -- --check, just clippy |
sqlx::query! or migrations | .sqlx/ regenerated and committed; migration works with the code already deployed |
Cargo.toml | cargo x deps --check |
apps/web | bun run check and bun run test for the touched features, in apps/web |
| User-visible web behavior | Exercised in a browser; docs/agent-guide updated if routes, editors, AI surfaces, or composer changed |
infra/ | bun run --cwd infra check; no deploy was run |
| New or changed flow, cross-service call, queue, or background job | Instrumented per the observability rule; trace verified connected in Tempo, or listed as not verified |
| Any behavior, API, name, or workflow change | Every doc that mentions it is updated: touched directories' AGENTS.md, docs/guides/, docs/architecture/, agent guide, READMEs, rules, skills (grep the changed names) |
| Config, env vars, service URLs | Every copy and Doppler step in the config rule is done or listed as a follow-up |
Deduplicate. Run one command per package, not per file.
Run each command. For rule bullets that no command covers, read the relevant diff hunks and judge. Don't stop at the first failure; finish the list.
One table, failures first:
| Result | Check | Source | Evidence |
|---|---|---|---|
| fail | cargo test -p calendar_service | area default | 2 failed: sync::tests::… |
| pass | Decorator reserves its height | web/lexical-nodes.md | Foo.tsx:40 sets aspect-ratio |
| skipped | Browser check | root guide | No browser in this environment |
A check is pass only if it ran or was verified in this audit. Explain every
skipped. Then list fixes for each failure; do not claim the work is done while
anything fails.
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.
Wrap a new backend endpoint in the TypeScript SDK (packages/sdk), or record it as skipped. Use when `just coverage` fails, or after adding an endpoint to a Rust service.
The English summary is being prepared. Showing the original description.
Add or change an in-app feature tour (a view's guided flyover) in the web app. Use when adding a tour to a view, adding or editing tour steps, pointing a step at a new control, or when a step's target needs something opened first.
The English summary is being prepared. Showing the original description.
Enforce hexagonal architecture in the Rust backend. Use before modifying crates/ or Rust services, especially inbound axum/tool/listener adapters, domain services/ports, outbound adapters, authorization, permissions, database access, or external clients.
The English summary is being prepared. Showing the original description.
Use when adding collaborative markdown, notes, or descriptions to a feature with collab surfaces. Covers parent entities, service entry points, authorization, content storage, and lifecycle.
The English summary is being prepared. Showing the original description.
Build a new AI tool end-to-end — Rust implementation, toolset wiring, infra, schema generation, and frontend UI.
The English summary is being prepared. Showing the original description.
Use when building a feature on reusable database storage or UI, such as CRM, or deciding whether it needs a Macro database entity. Covers shared storage, a host-independent database UI and API contract, ownership, authorization, and the _entities naming convention.
The English summary is being prepared. Showing the original description.