Run tests with coverage instrumentation, identify uncovered code, and produce kanban tasks for coverage gaps. Use when the user says "coverage", "what's untested", "find coverage gaps", or wants to know what needs tests.
Replace README.md wholesale with a minimal, high-quality README modeled on the best open source packages — it writes a complete new file, never an incremental edit of the old one. Two modes — `library` (no logo, leads with an inline runnable usage example) and `application` (logo, installation, getting started). Use when the user says "make a readme", "write the readme", "readme", "improve the README", or a new project needs one. Pass `library` or `application` to force the mode; otherwise it is detected from the project manifest.
Code review workflow. Use this skill whenever the user says "review", "code review", "review this PR", "review my changes", or otherwise wants a code review.
Monitor the performance of a sah /finish batch (the kanban implement→test→review→commit pipeline) running in a given project folder — locate the active finish session, report progress, scan for errors, quantify token usage by source, and surface sah tooling errors and behavior changes. Takes a project folder as its argument. Use when the user says "check sah", "watch the run", "monitor the finish run", "fire up the timer", "is the run healthy", "analyze token usage", or wants periodic status on a finish batch in a folder. Drives a self-paced 10-minute watch loop until the run completes.
Verify work before claiming it done. Use when the user says "really done", "are we done", "ready to ship", "ready to commit", "is this passing", or when about to claim work is complete, fixed, or passing. Also use before committing or creating PRs. Requires running verification commands and confirming output before any success claim — evidence before assertions, always.
Use before writing or changing production code — enforces strict test-driven development (RED, GREEN, REFACTOR) by writing the failing test first, watching it fail, then writing the code to pass. Use when the user says "tdd", "test first", "write the test first", "red-green-refactor", "write a failing test", or when implementing a new function, fixing a bug, or adding behavior that needs a regression test. Do NOT use for reading, exploring, or explaining existing code — use the explore skill instead. Do NOT use for running an already-written test suite — use the test skill. Do NOT use for pure refactors that add no new behavior and keep the existing tests green.
Drive kanban tasks from ready to done by looping implement → test → commit → review until each task is clean. Use when the user says "/finish", "drive tasks to done", "work the board", "finish the tasks", "finish the batch", or otherwise wants to orchestrate tasks through the full pipeline to done. Supports single-task mode (one task id) and scoped-batch mode (all ready tasks in a tag, project, or filter).
Turn an issue into finished work. Use when a GitHub issue URL (e.g. github.com/owner/repo/issues/123) is pasted, or when the pasted text is clearly the body of an issue (title + description, "Steps to reproduce", "Expected/Actual behavior", labels). Also fires on "/issue", "make a task from this issue", "implement this issue", "do this issue". Converts the issue into one or more kanban tasks and then drives them to done.