command-guide
Claude Code Command Selection Guide - Automatically recommend and select the right commands, agents, and skills in Claude Code. Use when: (1) user is unsure which command or tool to use, (2) needs to decide which agent/skill best fits the current task, (3) querying usage scenarios for /plan, /tdd, /compact, /loop and other commands, (4) understanding when to invoke planner, code-reviewer, build-error-resolver and other agents, (5) needs command cheat sheet or decision flowchart. Triggers: "which command to use", "which agent", "command selection", "how to use /plan", "when to use /compact", "agent selection guide", "command cheat sheet", "skill recommendation".
- Installs
- 512
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/alirezarezvani/claude-skills --skill command-guide- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads command-guide automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Claude Code Command Selection Guide
This skill helps you choose the most appropriate command, agent, or skill for different scenarios.
Quick Decision Flowchart
graph TD
A[User Request] --> B{Request Type?}
B -->|New Feature| C[/plan]
B -->|Bug Fix| D[/tdd or build-error-resolver]
B -->|Code Review| E[/code-review or code-reviewer agent]
B -->|Testing| F[/e2e or tdd-guide agent]
B -->|Context Too Long| G[/compact]
B -->|Documentation| H[/docs or docs-lookup agent]
B -->|Looping Task| I[/loop]
B -->|Security Review| J[security-reviewer agent]
C --> K[planner agent]
D --> L{Build Failed?}
L -->|Yes| M[build-error-resolver]
L -->|No| N[tdd-guide]
E --> O[code-reviewer]
F --> P[e2e-runner]
1. Built-in Slash Commands
Session Management Commands
| Command | Use Case | Example |
|---|---|---|
/compact | Context too long (>150K tokens), slow response, task phase transition | /compact or auto-trigger |
/clear | Start fresh conversation, clear history | /clear |
/loop | Periodic task execution, automated looping work | /loop 5m check build status |
/help | View help, learn commands | /help |
/fast | Need faster response (Opus 4.6 only) | /fast |
/model | Switch model | /model sonnet |
Development Workflow Commands
| Command | Use Case | Activation Timing |
|---|---|---|
/plan | Start new feature, architecture refactor, complex tasks | Enter Plan Mode |
/tdd | Write tests, TDD development workflow | When test guidance needed |
/e2e | E2E testing, critical user flow verification | When browser testing needed |
/code-review | Code quality review | After writing code |
/build-fix | Build failure, type errors | When build fails |
/learn | Extract patterns from session, learning | Before session ends |
/skill-create | Create new skill from git history | When repeating patterns found |
Documentation & Query Commands
| Command | Use Case | Example |
|---|---|---|
/docs | Update project documentation | /docs |
/update-codemaps | Update code maps | /update-codemaps |
/remember | Save memory to memory system | /remember user prefers concise output |
/tasks | View task list | /tasks |
2. Agents Selection
Development Workflow Agents
| Agent | Trigger Condition | Purpose |
|---|---|---|
planner | Complex feature request, architectural decision | Create implementation plan |
architect | System design, tech stack selection | Architecture analysis and decisions |
tdd-guide | New feature, bug fix | TDD workflow guidance |
code-reviewer | Invoke immediately after writing code | Code quality review |
security-reviewer | Handling auth, API, sensitive data | Security vulnerability detection |
Problem Solving Agents
| Agent | Trigger Condition | Purpose |
|---|---|---|
build-error-resolver | Invoke immediately when build fails | Fix build/type errors |
e2e-runner | Critical user flows, before PR | E2E test execution |
refactor-cleaner | Code maintenance, dead code cleanup | Dead code detection and cleanup |
doc-updater | Update docs, codemaps | Documentation sync |
Research & Exploration Agents
| Agent | Trigger Condition | Purpose |
|---|---|---|
Explore | Codebase exploration, file finding | Quick codebase exploration |
general-purpose | Complex multi-step tasks | General task handling |
docs-lookup | Query library/framework docs | Get latest API documentation |
3. Skills Selection
Workflow Skills
| Skill | Trigger Timing | Purpose |
|---|---|---|
tdd-workflow | Developing new feature/fixing bug | Complete TDD workflow guidance |
verification-loop | After feature completion, before PR | Comprehensive verification (build/test/lint/security) |
strategic-compact | Long session, context pressure | Guide when to manually /compact |
Architecture & Pattern Skills
| Skill | Trigger Timing | Purpose |
|---|---|---|
frontend-patterns | Frontend development | React/Next.js/Vue best practices |
backend-patterns | Backend development | API/service architecture patterns |
api-design | API design | RESTful/API design standards |
mcp-server-patterns | MCP server development | MCP configuration and patterns |
Testing Skills
| Skill | Trigger Timing | Purpose |
|---|---|---|
e2e-testing | E2E testing needs | Playwright test generation |
security-review | Security review needs | OWASP Top 10 detection |
Research Skills
| Skill | Trigger Timing | Purpose |
|---|---|---|
deep-research | Need deep research | Multi-round search and research |
exa-search | Need web search | Web content search |
documentation-lookup | Query library docs | Context7 documentation query |
4. Scenario Decision Matrix
By Task Phase
| Phase | Recommended Tool Combination | Reason |
|---|---|---|
| Requirements Analysis | planner + Explore | Plan first, explore later |
| Architecture Design | architect + api-design skill | Professional architecture guidance |
| Pre-Development | tdd-guide + tdd-workflow skill | Test first |
| During Development | Direct edit + quick iteration | Stay in flow |
| Post-Development | code-reviewer + verification-loop | Quality gate |
| Testing Phase | e2e-runner + e2e-testing skill | Complete test coverage |
| Before PR | security-reviewer + verification-loop | Final verification |
| Build Failure | build-error-resolver | Focused fix |
By Problem Type
| Problem | Invoke Immediately | Note |
|---|---|---|
| Build failure | build-error-resolver | Minimal changes, quick fix |
| Type error | build-error-resolver | TypeScript specialist |
| Bug fix | tdd-guide | Write test then fix |
| Security vulnerability | security-reviewer | OWASP detection |
| Poor code quality | code-reviewer | Immediate review |
| Missing documentation | doc-updater | Auto update |
| Dead code | refactor-cleaner | Safe cleanup |
By Development Type
| Development Type | Skills Combination |
|---|---|
| Frontend feature | frontend-patterns + tdd-workflow |
| Backend API | backend-patterns + api-design + tdd-workflow |
| MCP server | mcp-server-patterns + tdd-workflow |
| Database | database-reviewer agent |
| Security feature | security-reviewer + security-review skill |
5. Parallel Execution Strategy
Parallelizable Scenarios
Recommended: Launch multiple independent tasks simultaneously
Scenario: Preparing PR after code completion
- Agent 1: code-reviewer (code quality)
- Agent 2: security-reviewer (security review)
- Agent 3: e2e-runner (E2E tests)
Scenario: Large refactor analysis
- Agent 1: architect (architecture analysis)
- Agent 2: Explore (code exploration)
- Agent 3: refactor-cleaner (dead code detection)
Sequential Execution Required
Cannot parallelize: Dependencies exist
Scenario: Fixing build error
- Sequence: build-error-resolver -> test verification -> code-reviewer
Scenario: New feature development
- Sequence: planner -> tdd-guide (write tests) -> implementation -> code-reviewer
6. Auto-Trigger Rules
Invoke Without User Request
| Situation | Auto Action |
|---|---|
| Code written/modified | Immediately invoke code-reviewer |
| Build fails | Immediately invoke build-error-resolver |
| Complex feature request | Immediately invoke planner |
| Handling auth/sensitive data | Immediately invoke security-reviewer |
| New feature/bug fix | Immediately invoke tdd-guide |
| Architectural decision | Immediately invoke architect |
7. Context Management Timing
| Indicator | Trigger /compact |
|---|---|
| Token > 150K | Immediately compact |
| Slow response | Suggest compact |
| Task phase switch | Compact at boundary |
| Major milestone completed | Compact then continue |
| Debugging ends -> new task | Clear debug traces |
Best Practices:
- Compact after research, before implementation (preserve plan)
- Compact after milestone completion (clear intermediate state)
- Don't compact mid-implementation (lose variables/paths)
8. Command Cheat Sheet
Development Workflow:
/plan -> Enter planning mode (complex tasks)
/tdd -> TDD workflow
/e2e -> E2E testing
/code-review -> Code review
/build-fix -> Fix build
Session Management:
/compact -> Compact context
/clear -> Clear session
/loop -> Looping task
/fast -> Fast mode
Documentation & Memory:
/docs -> Update docs
/remember -> Save memory
/tasks -> View tasks
Help:
/help -> View all commands
9. Usage Examples
Example 1: New Feature Development
User: Add user authentication feature
Workflow:
- /plan -> planner agent creates plan
- tdd-guide -> write tests
- Implementation -> edit code
- code-reviewer -> code review
- security-reviewer -> security review (auth sensitive)
- e2e-runner -> E2E tests
- /compact -> compact after milestone completion
Example 2: Build Failure
User: npm run build failed
Workflow:
- build-error-resolver -> analyze error, minimal fix
- Verify build success
- code-reviewer -> check fix quality
Example 3: Code Refactoring
User: Refactor authentication module
Workflow:
- architect -> architecture analysis
- planner -> implementation plan
- refactor-cleaner -> dead code detection
- tdd-guide -> ensure test coverage
- Implementation -> refactor code
- verification-loop -> comprehensive verification
Core Principles:
- Plan first, implement later - Use
/planfor complex tasks - Test first - Use
tdd-guidefor new features - Review immediately after coding - Use
code-reviewerwhen code complete - Fix build immediately when failed - Use
build-error-resolver - Review sensitive code - Use
security-reviewerfor auth/API - Verify comprehensively before PR - Use
verification-loop
FAQ
What does the command-guide skill do?
Claude Code Command Selection Guide - Automatically recommend and select the right commands, agents, and skills in Claude Code. Use when: (1) user is unsure which command or tool to use, (2) needs to decide which agent/skill best fits the current task, (3) querying usage scenarios for /plan, /tdd, /compact, /loop and other commands, (4) understanding when to invoke planner, code-reviewer, build-error-resolver and other agents, (5) needs command cheat sheet or decision flowchart. Triggers: "which command to use", "which agent", "command selection", "how to use /plan", "when to use /compact", "agent selection guide", "command cheat sheet", "skill recommendation".
How do I install command-guide?
Run npx skills add https://github.com/alirezarezvani/claude-skills --skill command-guide in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/command-guide/ (personal) or .claude/skills/command-guide/ (project).
Which AI agents can use command-guide?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is command-guide safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains command-guide?
It is published by alirezarezvani in alirezarezvani/claude-skills. It has 512 recorded installs.
More from alirezarezvani/claude-skills
engineering-skills
alirezarezvani/claude-skills
Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need, never bulk-load the bundle.
finance-skills
alirezarezvani/claude-skills
Router/index for the finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts), saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio) and month-end-close (close calendar, reconciliations, flux review). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics').
marketing-skills
alirezarezvani/claude-skills
Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.
business-growth-skills
alirezarezvani/claude-skills
Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').
engineering-advanced-skills
alirezarezvani/claude-skills
Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops.
product-skills
alirezarezvani/claude-skills
Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.