Loading...
Loading...
Found 26 Skills
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.
Session mode: act as orchestrator brain only. Research and implementation go to cheaper-model subagents; the orchestrator scopes, briefs, verifies, and judges. User-invoked with the task as the argument.
Comet Phase 4: Verification and Wrap-up. Invoke with /comet-verify. Verify that implementations comply with designs and handle development branches.
Refactor CLAUDE.md files to follow progressive disclosure principles. Use when CLAUDE.md is too long or disorganized.
Code review practices emphasizing technical rigor, evidence-based claims, and verification. Use when receiving code review feedback, completing tasks requiring review, or before making completion claims.
Iterative execution methodology. Small steps, verify each, adapt based on results.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing.
Use when building anything non-trivial. Enforces a spec → plan → execute → verify loop that prevents "looks right" failures. Creates spec.md, todo.md, and decisions.md before writing code.
Execute individual plan phases as background sub-agents for context-efficient implementation.
Full ceremony mode for the whole suite. Run /deep before risky or ambiguous work; /deep off returns to fast-first.
Implement technical plans from thoughts/shared/plans with verification