Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Code review practices with technical rigor, design review, and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, evaluating whether PR changes need redesign, or preventing false completion claims in pull requests.
Triage and address unresolved GitHub PR review comments and fix failing CI checks: validate feedback (do not assume comments are correct), mark with eyes, thumbs up/down for address vs push back, implement fixes, commit and push. Use when the user asks to address PR comments, triage review feedback, fix failing checks, respond to PR review, or invokes /fix-pr.
Review an implementation plan for clarity gaps, blind spots, missing assumptions, and risky ambiguities, then produce an improved version.