Skill Claude Code
How to write good tests. Use when writing tests, improving test coverage, or evaluating test quality. Also invoked by other skills — BDD at RED phase, tdd-review at GREEN gate, refactor at PROTECT phase, and debug. Core test quality knowledge across all workflows.
Skill Claude Code
Ticket system and work logs for context anchoring. Use when creating tickets, managing work logs, or anchoring context across multi-step tasks or sessions. Do NOT use for simple patches or single-step tasks.
Skill Claude Code needs its repo
Verify ticket completion criteria — use when finishing a ticket, before marking work done, or checking acceptance criteria. Runs tests, build, lint, scenarios, and dependency drift checks.
Skill Claude Code
Safeword semver commitment and release discipline. Use when bumping versions, cutting releases, deciding what goes in a patch vs minor vs major, or reviewing changelog entries. Also use when auto-upgrade logic needs to know what's safe to apply silently.
Command Claude CodeCursor
Run comprehensive code audit for architecture, dead code, and test quality.
Command Claude CodeCursor
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 Claude CodeCursor needs its repo
Kill zombie dev servers and test processes for this project.
Command Claude CodeCursor
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 Claude CodeCursor
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 Claude CodeCursor
Plain-English view of any safeword block, verdict, ticket, or your current state (project).
Command Claude CodeCursor
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 Claude CodeCursor
Run bounded linters and formatters for changed files (project).
Command Claude CodeCursor
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 Claude CodeCursor
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 Claude CodeCursor
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 Claude CodeCursor
Red-teams a ticket's test scenarios for gaps — cases that would pass even though the feature is broken (project).
Command Claude CodeCursor needs its repo
Self-review the spec inline and earn its Tier 1 review stamp (project).
Command Claude CodeCursor
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 Claude CodeCursor
How to write good tests — quality knowledge for any testing context.
Command Claude CodeCursor
Verify ticket completion criteria — tests, build, lint, scenarios, dependency drift.
Cursor rule Cursor
USE WHEN starting feature work, running /bdd, resuming a BDD ticket, or user says 'add', 'implement', 'build', 'feature', 'resume', 'continue'. Orchestrates BDD phases.
Cursor rule Cursor
USE WHEN in BDD intake phase OR ticket has phase:intake. Guides discovery and context gathering for features.
Cursor rule Cursor
USE WHEN in BDD done phase (verify.md exists). Close the ticket — verification already happened in verify.
Cursor rule Cursor
USE WHEN in BDD plan-implementation phase. Author impl-plan.md, run figure-it-out on load-bearing choices, ADR lifecycle, review before implement.
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: