ai-debt-detectorAudit recently generated or AI-assisted code for the debt patterns machine generation produces specifically, such as swallowed errors, resources opened without a cleanup path, unhandled edge inputs, imports and API methods that do not exist, and silent drift from the project's own conventions, and f
avoid-ai-writingAudit prose for the patterns that make it read as machine-generated and either flag them, rewrite the text, or produce a span-by-span edit list for a prose file, without adding a personality the author never had. Use when asked to remove AI-isms, clean up a README, changelog, release note, PR descri
code-reviewReview the changes between HEAD and a fixed point (a commit, branch, tag, or merge-base) on two separate axes, Standards and Spec, and report them side by side without merging the verdicts. Use when asked to review a branch, a feature in progress, or "everything since X", and when a change must be j
discernment-nudgeAfter a substantive answer the user may act on (a recommendation, an estimate, an interpretation of data, a drafted plan or proposal, a multi-step argument), append two or three specific follow-up questions that help them check a fact, probe an assumption, or notice missing context. Fires at most on
production-auditAudit a repository for production readiness from local evidence only, covering security, data integrity, payments and webhooks, operations, user-facing failure states, secret exposure, an OWASP-style sweep, and modules that are shallower than their surface suggests. Use before a launch or rollout, a
receiving-code-reviewEvaluate incoming code-review feedback before anything is changed, by restating each item, verifying it against the codebase, and answering with a technical acknowledgement or a reasoned pushback instead of reflexive agreement. Use when review comments arrive from a person, a tool, or another agent,
requesting-code-reviewPackage a completed change into a self-contained review brief (what was built, what it was meant to do, the exact commit range) and obtain a severity-ranked review against it, either from a fresh session-scoped reviewer or inline. Use after finishing a task or feature, before merging, before a risky