
Unified review dispatcher. Auto-detects review type from argument or presents selection menu. Routes to code review, PR review, or scope review.
Unified scope lifecycle. Auto-detects operation from argument or presents selection menu. Routes to create, review, update, done, or list.
Modern git workflows plus dispatched operations (rebase strategy analysis). Use when managing branches, structuring commits, choosing development strategies, or planning a rebase.
External code-review harness (`peer` zsh tool): canonical model registry, idle-stall watchdog, and self-parallelising fan-out to codex/gemini. Use when dispatching external (non-Claude) reviewers from the review or implement pipelines — call `peer run`/`peer <harness>` instead of `codex exec`/`gcloud`+Vertex directly.
Scope execution pipeline and implementation methodology. Use for executing scopes (TDD three-phase pipeline), verifying completion, debugging, or building features from requirements.
Resume interrupted work from context. Use when continuing after session break, context limit, or interruption.
Code domain. Composes with implement, review, and test skills for code-specific operations.
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
Intent router. Auto-detects execution mode from context and routes to the appropriate skill.
Query code intelligence with gestalt. Use when finding callers/callees, tracing references, running CozoScript queries, or generating repo maps.
GitHub issue operations. Use when creating PRs from issues, viewing issue details, or linking issues to branches.
Autonomous implementation loop over a focus topic. Reads active scopes, enumerates tasks as todos, then iterates the TDD pipeline (tester→implementer→reviewer) until all tasks are complete. Use when autonomously implementing all pending work for a scope or topic without manual step-by-step oversight.
Access language-specific coding guidelines from loqui. Use when implementing code and needing patterns, style guidance, or best practices for Python, Go, Rust, or Bash.
Create new Claude Code skills following project patterns and best practices. Use when building new skills, extracting reusable capabilities, or converting commands to skills.
Manage dotfiles using dotter (symlink manager and templater). Use when deploying, adding, removing, or organizing configuration files in ~/dotfiles.
Start structured red vs. blue team debates via subagents. Use when exploring a topic from multiple adversarial perspectives.
Unified validation dispatcher. Auto-detects validation type from argument or presents selection menu. Routes to test, implement (verify), or hooks-test.
Push into adversarial focus mode — surface orthogonal observations, run three rounds of named adversarial analysis (pre-mortem, devil's advocate, falsification), drop narration. Use when work is experimental, when a solution "looks correct," or when pattern-matching might be masking the real problem.
Ultra-concise bash command patterns. Use when constructing shell commands or one-liners.
Test-driven development methodology (RED-GREEN-REFACTOR). Use when implementing features, fixing bugs, or changing behavior - write failing test first, then minimal code to pass.
Resolve ambiguities interactively with tracked changes. Works with scope, code review, and other skills.