Skip to main content
ClaudeWave
EN, English

Claude Code Slash Commands · page 4

Slash commands for Claude Code collected from the directory: prompt definitions you can install into ~/.claude/commands with one command.

928 slash commands1-command install
  1. Understand the current state of the git repository

  2. plan3.9k

    Creates a concise engineering implementation plan based on user requirements and saves it to specs directory

  3. Creates a concise engineering implementation plan based on user requirements and saves it to specs directory

  4. prime3.9k

    Load context for a new agent session by analyzing codebase structure, documentation and README

  5. Load context for a new agent session by analyzing codebase structure and README

  6. Answer questions about the project structure and documentation without coding

  7. Manage, organize and ships your codebase.

  8. five3.5k

    Apply the Five Whys root cause analysis technique to investigate an issue

  9. pr3.5k

    Create a branch, split changes into logical commits, and open a pull request

  10. review3.5k

    Run a multi-perspective PR review (product, dev, QA, security, DevOps, UX) and post it to GitHub

  11. tdd3.5k

    Development practices and TDD workflow to follow before starting a feature

  12. test3.5k

    LLM unit testing best practices checklist for testing internal logic, not API endpoints

  13. todo3.5k

    Manage project todos in todos.md file

  14. ux3.5k

    User Experience Designer & UI Specialist persona for design-focused tasks

  15. Build a feature using Research > Plan > Implement phases

  16. doctor2.9k

    Diagnose pro-workflow setup and Claude Code configuration

  17. Train a skill's SKILL.md by running a SkillOpt-flavored offline loop over accumulated learn-rule corrections

  18. ship2.9k

    Commit all changes, push branch, create/update PR, and run local validation

  19. Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

  20. gate2.9k

    Run every objective gate this project can prove and report the real N/N. Use before claiming any screen or component is done.

  21. Scaffold a new design-product project that matches the recommended Claude Code layout (the reference structure). Use when starting a fresh product/app that will be built with this design system.

  22. ship2.9k

    Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.

  23. Perform competitive analysis on companies or products

  24. Fact-check claims or verify information

  25. Research current market trends in a specific industry or domain

  26. Start a focused research session on any topic

  27. Summarize all current research findings

  28. Say hello

  29. health2.7k

    Check running Claude Code or Codex sessions, find zombies, offer to clean up safely

  30. quick2.7k

    Quick 10-second context health check with quality score and top issues

  31. Create a detailed implementation plan using Codex 5.2 with high reasoning

  32. Draft a professional email using the What-Why-How framework. Use when you need to compose emails to colleagues, stakeholders, or leadership.

  33. Build a mental model of changes by splitting them into smaller logical chunks

  34. Sync feature branch with the latest main branch.

  35. Sync root README.md with current skills inventory from skills/ directory

  36. Transform a raw tweet idea into an optimized viral post for X

  37. Initialize the current project with Scientific Writer - a deep research and writing tool that combines AI-driven research with well-formatted written outputs.

  38. Guided Apify Actor development with best practices and systematic workflow

  39. Renamed → /portaljs-add-chart. This alias will be removed next minor release.

  40. Renamed → /portaljs-add-dataset. This alias will be removed next minor release.

  41. Renamed → /portaljs-add-map. This alias will be removed next minor release.

  42. Renamed → /portaljs-add-resource. This alias will be removed next minor release.

  43. Renamed → /portaljs-architect. This alias will be removed next minor release.

  44. Renamed → /portaljs-check-data-quality. This alias will be removed next minor release.

  45. Renamed → /portaljs-connect-ckan. This alias will be removed next minor release.

  46. Renamed → /portaljs-define-schema. This alias will be removed next minor release.

  47. deploy2.4k

    Renamed → /portaljs-deploy. This alias will be removed next minor release.

  48. Renamed → /portaljs-migrate. This alias will be removed next minor release.

  49. Renamed → /portaljs-new-portal. This alias will be removed next minor release.

  50. List pentest-ai agents relevant to a domain or tag (web, ad, cloud, mobile, recon, etc.).

  51. Recommend the right pentest-ai agent and concrete next steps for a freeform task description.

  52. cm2.2k

    Stage all files and create a commit.

  53. cp2.2k

    Stage, commit and push all code in the current branch

  54. create2.2k

    Create a new agent skill

  55. pr2.2k

    Create a pull request

  56. Utilize tools of Model Context Protocol (MCP) servers

  57. Postmortem analysis of cluster failures → OPTIMIZE PROMPTS to work for EVERY use case

  58. 启动 NanoClaw 智能体 (Agent) REPL — 一个由 claude CLI 驱动的持久化、会话感知 (session-aware) 的 AI 助手。

  59. e2e2k

    使用 Playwright 生成并运行端到端测试。创建测试旅程、运行测试、捕获截图/视频/追踪,并上传产物。

  60. 分析直觉(Instincts)并建议或生成进化的结构

  61. 增量修复 Go 构建错误、go vet 警告和 linter 问题。调用 go-build-resolver 智能体(Agent)进行最小化、外科手术式的修复。

  62. 针对地道模式、并发安全、错误处理和安全性的全面 Go 代码审查。调用 go-reviewer 智能体 (Agent)。

  63. 为 Go 强制执行测试驱动开发(TDD)工作流。先编写表格驱动测试(Table-Driven Tests),然后进行实现。使用 go test -cover 验证 80% 以上的覆盖率。

  64. Export instincts from project/global scope to a file

  65. 从文件或 URL 导入直觉(Instincts)到项目/全局作用域

  66. 显示已学习的直觉(项目 + 全局)及其置信度

  67. 从会话中提取可复用的模式(Patterns),在保存前进行质量自评,并确定合适的保存位置(全局 vs 项目)。

  68. 重述需求、评估风险并制定分步实施计划。在修改任何代码之前,必须等待用户确认(CONFIRM)。

  69. 列出已知项目及其直觉(instinct)统计数据

  70. 将项目级直觉(Instincts)提升至全局作用域

  71. 针对 PEP 8 合规性、类型提示、安全性和 Pythonic 风格的全面 Python 代码审查。调用 python-reviewer 智能体(Agent)。

  72. 配置你偏好的包管理器 (npm/pnpm/yarn/bun)

  73. 分析本地 Git 历史以提取编码模式并生成 SKILL.md 文件。Skill Creator GitHub App 的本地版本。

  74. tdd2k

    强制执行测试驱动开发工作流。先搭建接口脚手架,首先生成测试,然后编写最少代码以通过测试。确保 80% 以上的覆盖率。

  75. Add todo item to TO-DOS.md with context from conversation

  76. Gather requirements through adaptive questioning before executing any task

  77. Audit slash command file for YAML, arguments, dynamic context, tool restrictions, and content quality

  78. Audit subagent configuration for role definition, prompt quality, tool selection, XML structure compliance, and effectiveness

  79. List outstanding todos and select one to work on

  80. Invoke create-hooks skill for expert guidance on Claude Code hook development

  81. Create optimized prompts for Claude-to-Claude pipelines (research -> plan -> implement)

  82. Create hierarchical project plans for solo agentic development (briefs, roadmaps, phase plans)

  83. Create a new prompt that another Claude can execute

  84. Create a new slash command following best practices and patterns

  85. Create specialized Claude Code subagents with expert guidance

  86. Apply expert debugging methodology to investigate a specific issue

  87. Execute a PLAN.md file directly without loading planning skill context

  88. Delegate one or more prompts to fresh sub-task contexts with parallel or sequential execution

  89. Analyze the current conversation and create a handoff document for continuing this work in a fresh context

  90. Prepare and execute an Android release (patch/minor/major)

  91. Gather details and draft an actionable bug report for developers.

  92. Create a git commit with concise, bullet-point commit message

  93. Create a new plan document for tracking work.

  94. Run E2E tests in a dev container (isolated environment)

  95. Execute a plan document while keeping progress synchronized.

  96. Investigate a problem and align on the right next step before implementing.

  97. Investigate a Nimbalyst performance problem (freeze, lag, idle CPU, slow op, memory growth) with measured evidence before proposing a fix.

  98. Prepare and execute an iOS release (patch/minor/major)

  99. Create a visual UX mockup for a requested feature or screen.

  100. Summarize my recent git commits in standup format