parity-check
01Command Claude Code
Report safeword parity drift (pairs + contracts). Safeword-repo only.
Command Claude Code
Report safeword parity drift (pairs + contracts). Safeword-repo only.
Command Cursor
Run comprehensive code audit for architecture, dead code, and test quality.
Command Cursor
BDD orchestrator for feature-level work. Use when user says 'add', 'implement', 'build', 'feature', 'iteration', 'story', 'phase', 'resume', 'continue', or references a ticket/iteration/story. Also use when work touches 3+ files with new state/flows, or when user runs /bdd. Do NOT use for bug fixes, typos, config…
Command Cursor
Kill zombie dev servers and test processes for this project.
Command Cursor
Close a completed local delivery safely after verification. Use when wrapping up a finished coding session: merging only when you've been explicitly told to merge, running the retro, and cleaning up the exact merged branch and worktree.
Command Cursor
Finds the real cause of a bug, in four steps, before you touch a fix. Use when encountering bugs, test failures, unexpected behavior, or when previous fix attempts failed. Enforces investigate-first discipline ('debug this', 'fix this error', 'test is failing', 'not working').
Command Cursor
Plain-English view of any safeword block, verdict, ticket, or your current state (project).
Command Cursor
Internal fallback used only right after the shared review coordinator reports it's run out of reviewer routes. Not something a user invokes directly.
Command Cursor
Run bounded linters and formatters for changed files (project).
Command Cursor
Deep code review with web research. Use when the user says 'double check against latest', 'verify versions', or 'check security'. Adds live research on top of the automatic quality hook — confirms you're using current library versions and APIs, not stale ones.
Command Cursor
Systematic refactoring with small-step discipline. Use when user says 'refactor', 'clean up', 'restructure', 'extract', 'rename', 'simplify', or mentions code smells. Enforces one change → test → commit when the commit can stay scoped. For structural improvements, NOT style/formatting (use /lint). NOT for adding…
Command Cursor
Run a safeword retrospective on the current session on demand — mine the transcript for friction (bugs / rough edges / gaps) and submit it through the outbound safety check before filing upstream. Use when the user says "run a retro", "/retro", or wants to capture friction before the session ends.
Command Cursor
Red-teams a ticket's test scenarios for gaps — cases that would pass even though the feature is broken (project).
Command Cursor
Self-review the spec inline and earn its Tier 1 review stamp (project).
Command Cursor
Run a quick, throwaway experiment to answer one open technical question before committing to the real build. Only runs when you ask for it directly.
Command Cursor
How to write good tests — quality knowledge for any testing context.
Command Cursor
Verify ticket completion criteria — tests, build, lint, scenarios, dependency drift.
Command Cursor
Tests whether a proposed product bet has credible demand. Use when Why now depends on an unresolved, decision-critical demand claim or when the user explicitly asks for demand research. Do NOT use for child features, mandated work, parity work, or when a cheaper experiment can answer the question first.
Command Cursor
Prepare a pull request for human review and decide whether it may leave Draft. Use when creating or rewriting a PR description, marking a PR ready, responding to review, or checking mergeability.
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: