Root-causes a failing test, exception, or wrong behavior via hypothesis elimination, in an isolated context. Use when the cause isn't obvious. Returns a distilled diagnosis + a minimal reproduction — it does not apply the fix (that happens under the bug-fix procedure).
Grades a change against its spec, check by check, and posts an advisory verdict. Use before a PR is approved, or invoke locally before pushing. The grader NEVER grades its own work — it runs in a fresh context and did not write the code.
Produces an implementation plan for a spec before code is written. Use for any MEDIUM or HIGH spec, or any feature touching 5+ files / a new service. Returns a sequenced plan with files to touch, order of changes, risks, and unknowns — it does NOT write code.
Reviews changes on gated paths or HIGH-risk specs for security defects. Use PROACTIVELY when a change touches auth, identity, payments, PII, migrations, infra, the pipeline, or prompt/model/tool definitions. BLOCKS on a HIGH-severity finding; advises otherwise.
Reviews user-facing Angular changes for UX quality: every state exists (loading, empty, error, success), accessibility basics hold, components follow the codebase's existing patterns, and the flow works end-to-end. Angular-aware — also catches the framework's own failure modes. Use PROACTIVELY when a change adds or…
Add a new endpoint / MediatR command or query / handler / service the way this .NET codebase already does it. Use when building an API surface, a CQRS handler, a controller, a validator, or a DI registration in a .NET / Clean Architecture repo. Finds the one canonical example and mirrors its layering, validation…
Add a new endpoint / route / use case / service the way this Node + TypeScript codebase already does it. Use when building an API surface, a request handler, a validator, a port/adapter, or a container registration in a Node/TypeScript repo. Finds the one canonical example and mirrors its layering, validation, error…
Add a new module / CLI command / service function / loader the way this Python codebase already does it. Use when building a public surface, a command entry point, a data loader, a validator, or a new package module in a Python / uv repo. Finds the one canonical example and mirrors its layering, typing, error model…
Add a new endpoint / handler / service the way this codebase already does it. Use when building an API surface, a CQRS handler, a controller, or a service registration. Finds the one canonical example and follows it exactly — so agents reuse the established pattern instead of inventing a new one each run.
The team's bug-fix procedure: reproduce with a FAILING TEST first, then fix, then prove the test passes. Use whenever a bug is reported. Do not start by patching — start by reproducing. For deep root-cause hunts, invoke the debugger agent from inside this procedure.
Build a golden set for an agentic (LLM-powered) spec — the acceptance criteria for probabilistic behavior. Use when a spec's deliverable is an agent/prompt/tool and needs evals before build, or when adding cases from a production failure. Produces a versioned golden-set.yaml under eval-datasets/specs/ /, referencing…
Open a spec's PR correctly: the right branch, a conventional-commit title, a body that maps the diff to the spec's acceptance checks with a test plan, and the spec file included in the diff. Use when a change is ready to push for review.
Turn a backlog story into a Definition-of-Ready spec at specs/NNNN-name.md. Use when the user wants to "write a spec", "make this story ready", or start a feature. Enforces the vague-line test on every acceptance check and assigns a risk tier. Use BEFORE delegating any build — no spec, no build.
Write tests that encode WHY behavior matters, mapped to a spec's acceptance checks. Use when adding tests for a feature or reproducing a bug. For bug fixes, write the failing test FIRST. Targets the team's coverage bar on new code.
★not rated 2 21d agoA52 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: