Skip to main content
ClaudeWave

Claude Code Slash Commands · page 8

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

1,123 slash commands1-command install
  1. Show recent memories and activity timeline

  2. Search memories for specific content or patterns

  3. Show memory statistics and storage information

  4. Extract design patterns from code into specs and wiki

  5. Guided reading of code or wiki to extract patterns

  6. Investigate questions with hypothesis testing and evidence logging

  7. Get alternative perspectives — review, challenge, or consult

  8. Generate overlays to fix workflow command deficiencies

  9. Use when a topic needs structured multi-dimensional investigation before planning or decision-making

  10. Generate formal specification package (Product Brief, PRD, Architecture, Epics) through 6-phase document chain

  11. Use when exploring ideas, evaluating approaches, or needing multi-perspective analysis before implementation

  12. Use when a question needs cross-verification from multiple CLI tools or diverse analytical perspectives

  13. Compose reusable workflow templates from natural language

  14. Use when a confirmed plan is ready for implementation

  15. Use when stress-testing a plan, idea, or requirement against codebase reality before brainstorming

  16. Audit current milestone for cross-phase integration gaps

  17. Archive completed milestone and prepare for next

  18. Bump version, generate changelog, tag milestone

  19. Use when creating, revising, or verifying an execution plan for a phase or task

  20. Play workflow templates with checkpoint resume

  21. Quick task execution, skip optional agents

  22. Self-running loop controller for adaptive maestro workflow — build, tick, decide in one skill

  23. Execute next pending step in ralph session

  24. Generate roadmap with milestone/phase structure from requirements or upstream context

  25. Parallel workflow accelerator — route intent to fixed Workflow scripts for multi-agent concurrent execution

  26. Load and execute tool specs by category or name

  27. Register tool specs - extract, generate, or optimize

  28. Extract design system from code, generate reference package, persist as knowledge assets

  29. Dynamic adversarial workflow generator — scan library, match or generate, execute, persist

  30. Rebuild all codebase documentation from scratch

  31. Extract knowledge from artifacts into wiki/spec/issues

  32. Discover issues via multi-perspective analysis

  33. Create, query, update, close, and link issues

  34. Analyze codebase patterns and generate .workflow/kg/extractors.yaml for custom symbol extraction

  35. Capture reusable knowledge as templates, recipes, or tips

  36. Manage knowhow entries (workflow and system)

  37. Audit and prune knowledge across spec / knowhow / artifact stores

  38. Show project dashboard with progress and next steps

  39. Manage wiki graph — health, cleanup, search, stats

  40. Long-running debug cycle — archaeology, diagnosis, fix, confirmation, generalization, discovery, and knowledge persistence

  41. Long-running codebase improvement cycle — multi-dimensional audit, deep diagnosis, targeted fix, verify, generalize, and engineering knowledge persistence

  42. Requirement-driven iterative cycle — plan, execute, strict verify, fix loop until acceptance criteria met

  43. Deep review + fix cycle — archaeology, exploration, multi-dimensional review, targeted fix, generalization, discovery, and knowledge persistence

  44. Long-running UI optimization cycle — visual survey, multi-dimensional audit, divergent exploration, fix, verify, generalize, and design knowledge persistence

  45. Use when test coverage needs automated expansion or existing tests need iterative convergence

  46. Use when bugs, test failures, or unexpected behavior need systematic root cause investigation

  47. Use when accumulated tech debt needs systematic identification and safe reduction

  48. Use after completing a phase to extract lessons, patterns, and improvement opportunities

  49. Use after execution to evaluate code quality across correctness, security, performance, and architecture

  50. Sync codebase docs by tracing git diff impact

  51. Register a domain term into project glossary

  52. Detect and realign .workflow/ artifact drift against code reality after refactoring

  53. Commit changes with auto-generated message showing command context, timestamp, and change count

  54. Add a new Claude Code hook event with sounds, config, settings, scripts, and docs

  55. Track Claude Code changelog and find what needs updating in this repo

  56. Run ad-hoc PostgreSQL analytics queries against dev/test database

  57. Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

  58. Generate a custom checklist for the current feature based on user requirements.

  59. Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

  60. Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

  61. Execute the implementation plan by processing and executing all tasks defined in tasks.md

  62. Execute the implementation planning workflow using the plan template to generate design artifacts.

  63. Create or update the feature specification from a natural language feature description.

  64. Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

  65. Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

  66. Analyze git changes and create a commit without Claude Code attribution

  67. auth533

    Configure OAuth providers, auth hooks, JWT lifetimes, and service keys for a Butterbase app

  68. Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase

  69. Develop, deploy, or debug a Butterbase serverless function

  70. idea533

    Stage 1 of the journey: concrete one-question-at-a-time idea brainstorm with inline Butterbase capability tagging.

  71. plan533

    Stage 2 of the journey: translate the idea + capability map into a concrete Butterbase plan (tables, RLS, auth, functions, storage, frontend).

  72. rag533

    Build a RAG knowledge base on Butterbase: ingest documents, run semantic search, generate synthesized answers

  73. Design or modify a Butterbase database schema using the declarative DSL

  74. Hackathon submission: assemble metadata from journey artifacts and call prep_and_submit_hackathon_entry.

  75. Guided version bump — validate, tag, and create GitHub release

  76. Run pre-release validation checks on all SKILL.md files and JSON databases

  77. Implement tasks from an OpenSpec change (Experimental)

  78. Archive a completed change in the experimental workflow

  79. Enter explore mode - think through ideas, investigate problems, clarify requirements

  80. Propose a new change - create it and generate all artifacts in one step

  81. Look up library documentation using Context7 MCP tools for a specific task

  82. url505

    Scrape and integrate documentation from provided URLs using Firecrawl tools

  83. Full autonomous security workflow — scan, dedup, prep, analyse, consensus, judge, exploit, patch, group

  84. Analyze existing SARIF findings with LLM

  85. Add, list, edit, or remove per-function annotations attached to source files

  86. Audit authentication (JWT, cookies) and security logging coverage automatically

  87. CodeQL deep static analysis with dataflow validation

  88. List all available MANTISHACK commands

  89. Autonomous crash root-cause analysis for C/C++ bugs

  90. CVE patch discovery — find, acquire, and diff the fix commit for a CVE

  91. Generate Mermaid visual maps from /understand or /validate output directories

  92. Generate exploit proof-of-concepts for vulnerabilities (beta)

  93. Binary fuzzing with AFL++ integration

  94. Evidence-backed forensic investigation for GitHub repositories

  95. Generate secure patches for vulnerabilities (beta)

  96. Manage MANTISHACK projects — create, list, status, coverage, findings, diff, merge, report, clean, export

  97. Software Composition Analysis — find vulnerable dependencies, gate CI, fix and pin

  98. Scan a repository with Semgrep and CodeQL

  99. Inspect per-model reliability across decision classes; answer natural-language questions about model competence

  100. Run automated workflow tests for all commands