Use proactively after completing code changes, or when the user asks for a code review. Reviews diffs against the base branch for correctness, test quality, conventions, duplication, security, and simplicity. Returns structured findings.
Checks if a PR is too large and suggests how to split it into smaller PRs. Analyzes diff size, logical groupings, and dependencies to recommend optimal splits. Target: max 400 added lines per PR.
Read-only codebase explorer for Spec-Driven Development. Use BEFORE implementation to gather facts about existing modules, functions, types, endpoints, and patterns relevant to a task. Returns a structured findings report with file:line citations. NEVER edits files. Stack-agnostic.
Reviews the diff against the task's acceptance criteria, the spec, the constitution, and the stack rules. Use AFTER the tester reports green and the verifier returns PASS. Returns approve / request-changes with cited issues. Read-only. Stack-agnostic.
The loop's verifier. Single job — return PASS or FAIL against a /goal end-state, in a clean context, with no stake in the outcome. Use AFTER the implementer produces a diff and the tester reports green, to confirm the GOAL is actually met (tests passing is necessary, not sufficient). Read-only on source; runs…
A meta-agent that improves another coding agent's instruction file after that agent has been used. It reviews what went wrong and updates the agent's documented rules.
A database migration checker that reviews planned changes to a database’s structure, such as adding, changing, or removing tables and columns. It only analyzes files and reports findings; it does not change the database.
Senior .NET backend expert. Applies the project's backend-pattern skill (devarch-module = MediatR CQRS / IResult / AOP by default; a project may declare its own). Use proactively — owns server behaviour: endpoints, handlers, validators, controllers, business rules, integrations. Any request about it is yours whatever…
Performance auditor. Use proactively when a change touches a hot path, a query/loop, a render path, a large payload, or when something is reported slow. Produces measured findings via performance; writes no fix.
Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, and ensures critical user flows work.
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.