Catalog
Every x402, MPP, MCP, and skill listing we've indexed, normalized, and enriched.
turboplan
Analyze task complexity and route to a mode by artifact: direct fix for clear-scope changes, plan file when the approach needs to be written down, or spec and shells for multi-session projects. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan
survey-patterns
Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to "survey patterns", "find existing patterns", "look for analogous features", "check how
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
stage-commit
Stage files and create a commit in one step with a message matching existing commit style. Use when the user asks to "stage and commit", "add and commit", "commit my changes", or "commit these changes".
stage-commit-push
Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".
split-and-ship
Execute an approved split plan by creating separate branches, commits, and PRs for each change group. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test"
simplify-code
Run a multi-agent review of changed files for reuse, quality, efficiency, and clarity issues followed by automated fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "cle
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
self-improve
Extract lessons from the current session and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "save learnings", "update CLAUDE.md with what we learned"
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what too
review-pr
Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".
review-plan
Review a planning artifact (plan, shells, or spec) by running internal and peer reviews in parallel and returning combined findings. Use when the user asks to "review my plan", "review my shells", "review my spec", "check my plan", "check my shells", "check my spec", "critique my
review-dependencies
Detect package managers and discover outdated or vulnerable dependencies. Returns structured findings without upgrading. Use when the user asks to "review dependencies", "check for outdated packages", "check dependencies", "scan dependencies", or "dependency review".
review-code
Review code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argume
review-agentic-setup
Detect agentic coding infrastructure in a project: CLAUDE.md, AGENTS.md, installed skills, MCP servers, hooks, and cross-tool compatibility (Claude Code and Codex CLI). Returns structured findings about agentic readiness without applying changes. Use when the user asks to "review
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comment
resolve-findings
Choose an implementation path (direct or plan) for evaluated findings and dispatch it. Direct path applies fixes directly; plan path runs /turboplan. Use after /evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "ap
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draf
refine-plan
Iteratively review and revise a planning artifact until no new findings survive evaluation. Supports plans, shells, and specs. Use when the user asks to "refine the plan", "refine the shells", "refine this spec", "iterate on the plan", "iterate on the shells", "tighten the plan",
recall-reasoning
Recall the reasoning behind a past change by locating the Claude Code transcript that produced it. Use when the user asks to "recall reasoning", "find reasoning", "look up reasoning", "recall implementation reasoning", "find the rationale", "why did I do X", "recall from transcri
polish-code
Stage, format, lint, test, review, smoke test, and re-run itself until stable. Use when the user asks to "polish code", "refine code", "iterate on code quality", "review loop", "clean up, test, and review loop", or "run the polish loop".
pick-next-shell
Pick the next shell whose dependencies are satisfied and carry it through planning: expand, refine, self-improve, halt. Use when the user asks to "pick next shell", "next shell", "continue project", "what's next", "next implementation step", or "continue with the plan".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize iss