Agent
Read-only auditor for a repo's agent-instruction system. Used by /instructions-audit (or directly) to sweep CLAUDE.md, .claude/, and .agent/ for broken pointers, dead/duplicate rules, contradictions with reality, cap breaches, and enforcement drift. Returns a severity-ranked findings list with file:line evidence…
Agent
Prior-art lookup — searches the project's .agent/lessons/ (plus .docs/) for lessons matching an error, symptom, or component, and returns the matches with relevance. Use PROACTIVELY before debugging a non-trivial error, so you reuse what past sessions already learned instead of re-deriving it. Never proposes fixes …
Agent
Verify that recent code changes comply with the project's pattern registry at .agent/patterns/. Read-only audit. Different from pattern-verifier (which checks the project's coding-style/convention rules) — this one audits against the formal per-topic pattern bodies in .agent/patterns/{topic}.md, checking shape…
Agent
Verify that recent code changes comply with the project's own coding-style / convention rules. Read-only review pass — outputs violations grouped by rule. Use as a fast code-shape check (e.g. the third pass in a fix → verify → fix-pass-2 chain) — lighter than the deeper pattern-compliance registry audit. Reads the…
Agent
Read-only drift audit of a repo's binding docs against code reality. Use after large refactors, before a release, or when docs feel stale — verifies CLAUDE.md, rules, agent memory, docs/, and any deploy contract still tell the truth. Returns a drift table with file:line evidence; never edits. Broader than…
Agent
Adversarial multi-tenant isolation review of a diff or module. Use proactively after changes to API routes, auth, tenant lifecycle (join/leave/delete), sharing, tokens, or offline/cache sync — and before any release of a multi-tenant app. Reports findings with file:line evidence and severity; read-only.
Agent
Run a semantic-bug review against changed files using a 7-item checklist (resource lifecycle, error handling, unbounded growth, idempotent cleanup, empty input, shutdown, unvalidated casts). Catches bugs that grep-based pattern checks miss. Use after architectural refactors or anytime resource/lifecycle code changed.…
Agent
Given a feature or topic name, verify the implementation matches what's documented in the project's specs (.docs/). Read-only diff between docs and code. Use when you suspect a feature has drifted from spec, before opening a PR, or as a verification step after a refactor. More targeted than a full drift audit — one…
Agent
Given a wireframe/mockup file (HTML) and the implementation file paths, identify functional gaps between the wireframe and the code (missing buttons, unhandled states, dropped error feedback, unimplemented modes). Use when a UI screen has been implemented and you want a third-party check that the wireframe's…