code
25Skill Claude Code
Delegate implementation work to the coder agent. Provide requirements or feature file path.
Skill Claude Code
Delegate implementation work to the coder agent. Provide requirements or feature file path.
Skill Claude Code
Implementation and verification phase. Runs implement → sweep → review → prove-it → complete. Takes a validated feature file from /plan-work and delivers a green PR. Use when the plan is ready and you just need to build it.
Skill Claude Code
Metacognitive checkpoint — analyze user intent before executing. Use standalone or let orchestrate/plan invoke it. Forces critical thinking about what the user actually wants.
Skill Claude Code
Classify work as bug/feature/refactor, run planning, create tasks from every acceptance criterion, then hand off to implementation. The task list is the contract.
Skill Claude Code
Create a feature file with acceptance criteria before implementation. Use when no specs/features/.feature file exists for the work.
Skill Claude Code
Research and planning phase for features. Runs intent → plan → challenge → readiness gate. Produces a validated feature file ready for /deliver-work. Use before implementation when the problem needs thinking, not just coding.
Skill Claude Code
Prove implementation correctness by mapping every acceptance criterion to concrete evidence (passing tests, command output, code grep). Use after /review passes, before marking a PR ready. Also use standalone when you want proof that work is actually done — not just 'I think it works.'.
Skill Claude Code
Refactor flow: triage complexity → gather criteria → baseline → implement → verify → review → complete. Simple refactors skip challenge/prove-it. Criteria come from the issue body.
Skill Claude Code
Run parallel code reviews: principles-reviewer (SRP/design), hygiene-reviewer (reuse/patterns/idioms), test-reviewer (pyramid/coverage), and security-reviewer (PII/secrets). Surfaces conflicts for human decision.
Skill Claude Code
Search for similar patterns, anti-patterns, or issues elsewhere in the codebase after a fix or feature. Use after implementing a fix to catch the same bug in other places, or proactively to audit for a known pattern.
Skill Claude Code
Review specs and tests for pyramid placement, quality, and efficiency (readability, speed, memory, caching, build serialization).
Skill Claude Code
Create a PR with a filled-in template. Use when: 'write pr', 'create pr', 'open pr', 'make a pr', 'ship it', or after implementation is done and user wants to open a PR.
Plugin Claude Code
Bundles 1 skill · 49 tokens together
Debate a design question with N agents arguing different positions, then synthesize a recommendation.
Skill Claude Code
PII-scrub and publish a skill from /.claude/skills/ to the public /claude-skills repo. Use when a skill is ready to share publicly.
Skill Claude Code
Rebase current branch on origin/main. Use when the user says 'rebase', 'rebase main', 'update from main', 'sync with main', or before opening a PR.
Skill Claude Code
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Skill Claude Code
Post a PR review request to a team Slack channel. Use when a PR is ready for review, all checks pass, and it needs human eyes.
Skill Claude Code
Spawn a sister Claude session in a new tmux window of the current tmux session, briefed with a delegated sub-thread. Use when the user says 'fork yourself into a tmux window', 'fork off to a window', 'spawn a sister', 'hand this off to a sister', '/tmux-window-fork', or when a side-investigation has grown large enough…
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: