Skip to main content
ClaudeWave

Slash Commands de Claude Code · página 9

Slash commands de Claude Code recopilados del directorio: definiciones de prompts instalables en ~/.claude/commands con un comando.

1123 slash commandsinstalación en 1 comando
  1. Binary fuzzing with AFL++ integration

  2. Evidence-backed forensic investigation for GitHub repositories

  3. Generate secure patches for vulnerabilities (beta)

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

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

  6. Scan a repository with Semgrep and CodeQL

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

  8. Run automated workflow tests for all commands

  9. Map attack surface, trace data flows, hunt vulnerability variants

  10. Validate that vulnerability findings are real, reachable, and exploitable

  11. Web application security scanner (alpha)

  12. One-shot MAXIMAL autonomous pentest — the full scan+validate pipeline PLUS a parallel red-team agent war-game, adversarially verified and stitched into a kill-chain Red Team Report.

  13. Run the blueprint-validator against an existing blueprint and report PASS/FAIL with specifics. Blueprints written before v2 will FAIL — they have no acceptance criteria. That is expected, not a bug. / Audita un blueprint existente con el validador; los blueprints v1 fallan porque no tienen criterios de aceptación.

  14. Design a change against an existing codebase — maps the repo's stack, conventions, structure and tests, then emits a blueprint for a feature, refactor, or migration instead of a from-scratch build. / Diseña un cambio sobre un repo existente — mapea stack y convenciones y emite un blueprint de cambio, no de proyecto nuevo.

  15. Resume a build — reads tasks.json from a bundle, finds the first pending task whose dependencies are all done, and prints it with its epic, acceptance criteria, and every verify command. This is what lets a long build survive across sessions. / Reanuda una construcción desde tasks.json y muestra la siguiente tarea desbloqueada.

  16. Fast-track blueprint — three questions, smart defaults for everything else, still validator-gated. For when you just want it built. / Blueprint express — tres preguntas, defaults inteligentes, con el mismo validador.

  17. Re-verify every pinned version in an existing blueprint against the live registries and report what moved, what breaks, and what to change — un-rots a months-old blueprint without a redesign. / Reverifica cada versión fijada en un blueprint contra los registros y reporta qué cambió y qué romper.

  18. Quick job evaluation. Paste a JD and get a score plus one-paragraph summary. Faster than a full evaluate. Use when someone says 'quick eval', 'quick score', or 'just give me a number'.

  19. Set up your job search profile. Paste your resume or answer a few questions. Takes 5 minutes. Needed before evaluating jobs.

  20. Control thinking token limits via environment variable

  21. Run complete two-agent validation on module+tests (contract extraction + test validation). Binary pass/fail with specific issues.

  22. Pick up an open issue from the amux issue tracker, mark it doing, work it, and mark it done.

    mixpeek/amuxInstalar
  23. Use when the user says "add to board", "create a task", or wants to track a todo on the amux kanban board

    mixpeek/amuxInstalar
  24. amux446

    Use when you need to interact with the amux system — manage board tasks, check sessions, send emails, automate browsers, or work with CRM contacts

    mixpeek/amuxInstalar
  25. Use when the user asks to interact with a web page, take a screenshot of a site, click or type in Chrome, scrape content, or debug a web UI. Connects to real Chrome tabs with existing logins.

    mixpeek/amuxInstalar
  26. Scaffold a closed orchestrator loop — creates the mission note, state/constraints notes, and a scheduler entry from the v2 template.

    mixpeek/amuxInstalar
  27. Use when the user needs to log into a website for browser automation, save auth cookies, or sync browser profiles to cloud

    mixpeek/amuxInstalar
  28. Use when you need to test the amux dashboard UI, investigate a visual bug, or verify a frontend change works correctly

    mixpeek/amuxInstalar
  29. Use when the user wants to record a video of a browser task, create a screen recording, or produce an MP4 demo

    mixpeek/amuxInstalar
  30. Use when the user asks what a session did, wants to review session history, or needs to find errors in a session log

    mixpeek/amuxInstalar
  31. Use after making changes to the amux server or dashboard to verify the dashboard and APIs are working correctly

    mixpeek/amuxInstalar
  32. Perform comprehensive data analysis on specified dataset

  33. 自动化完成整个数据分析工作流程,从数据质量检查到最终报告生成

  34. Generate analysis code in specified language and analysis type

  35. Generate research hypotheses and experimental designs based on data patterns

  36. Perform data quality validation, checks, and monitoring for specified dataset

  37. Generate comprehensive analysis reports for specified dataset

  38. Create data visualizations for the specified dataset

  39. Competitive intelligence analysis with keyword gaps and opportunities identification

  40. Complete ASO audit with keyword research, competitor intelligence, metadata optimization, and launch planning

  41. Quick metadata optimization for Apple App Store and Google Play Store with copy-paste ready content

  42. Generate comprehensive pre-launch checklist and timeline with specific dates for app store submission

  43. Create smart commit with quality checks and conventional format

  44. Create pull request with proper validation

  45. Initialize ClaudeForge CI/CD system

  46. Create GitHub release with automated notes

  47. |

  48. do419

    Smart router: classify requests and route to the correct agent + skill

  49. Generate project-specific CLAUDE.md from repo analysis.

  50. Triage GitHub notifications: fetch, classify, report actions needed.

  51. Verify installation, diagnose issues, and guide first-time setup

  52. Comprehensive PR review using specialized agents, with automatic retro knowledge capture

  53. Learning system interface: stats, search, graduate learnings. Backed by learning.db (SQLite + FTS5).

  54. |

  55. Run the complete 34-stage implementation workflow for a large, multi-system, multi-wave, or CPU-delegated 5 Star Booker GM program.

  56. Diagnose and prune bloated Claude Code context. Run to slim down the current session before compacting or resuming.

  57. Commit what is already staged — runs the commit subagent in the background, following the ATLAS commit convention.

  58. Interview Boss about the project, then reason from first principles to design the ideal ATLAS operating identity/system-prompt for it — free to drop KISS/YAGNI/DRY/clean-architecture entirely when the project (and the LLM's own distribution) calls for a different mindset

  59. Initialize project context — understand the project, configure conventions, and set up project rules

  60. Brainstorm an idea into a clickable multi-screen React prototype — model the mind (Theory of Mind), interview to kill ambiguity, build a no-build CDN-React prototype under misc/prototypes/, run it, iterate until it matches Boss's vision.

  61. Quickly sketch a standalone low-fidelity wireframe as self-contained HTML — gray boxes, dashed borders, no framework. Lighter than /plan:create-phase, static unlike /brainstorm:prototype.

  62. Discover the project's visual identity, prototype 3 HTML design variants for Boss to compare in a browser, iterate, then lock in DESIGN.md (Stitch-format, machine + human readable). The single source of truth AI coding agents read before generating UI.

  63. log395

    Show recent git commits with a brief summary and continual context tied to the working directory / staging area.

  64. Stage and commit all working-directory changes — runs the commit subagent in the background until the tree is clean.

  65. Create a development phase the lean way — resolve ambiguity through Q&A, then capture it as a self-contained low-fidelity wireframe HTML document you implement from in plan mode

  66. Guided feature development with codebase understanding and architecture focus

  67. Author human-readable manual test cases (markdown) into docs/living-test-cases/ — the living artifact that /qa:manual-test-run executes

  68. One-shot an app autonomously — free-will the founding fork, build with deliberate decisions at every trigger, then adversarial review and a conscious final pass before delivery

  69. Plan any change the lean way — resolve ambiguity through Q&A, optionally explore the codebase, then capture the result as a single self-contained, visual HTML document (diagrams, wireframes, matrices) you implement from in plan mode

  70. Analyze staged changes and organize them into intuitive atomic commits following conventional commits.

  71. Show Claude-Flow commands and usage

  72. Interact with Claude-Flow memory system

  73. Coordinate multi-agent swarms for complex tasks

  74. Apply expert UX/UI design thinking to design, redesign, enhance, or fix any interface element with meticulous craft and intentionality.

  75. Address code review feedback — corroborate, validate, and implement changes from a review's final.md.

  76. Create a new custom reviewer from a natural language description.

  77. Check OCR installation and verify all dependencies are available.

  78. List past OCR review sessions.

  79. map357

    Generate a Code Review Map to help navigate large, complex changesets.

  80. post357

    Post the current OCR review to a GitHub PR.

  81. Run an AI-powered multi-agent code review on your changes.

  82. List all available reviewer personas for code review.

  83. show357

    Display a past OCR review session.

  84. Sync reviewer metadata from markdown files to reviewers-meta.json for the dashboard.

  85. Translate a multi-reviewer code review into a single human-voice GitHub PR comment.

  86. Implement an approved OpenSpec change and keep tasks in sync.

  87. Archive a deployed OpenSpec change and update specs.

  88. Scaffold a new OpenSpec change and validate strictly.

  89. Review a given code review markdown document, GitHub PR review, or inline feedback — corroborate each point against actual code, then implement valid changes.

  90. ❓Ask - You are a task-formulation guide that helps users navigate, ask, and delegate tasks to the correc...

  91. 🧠 Auto-Coder - You write clean, efficient, modular code based on pseudocode and architecture. You use configurat...

  92. 🪲 Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...

  93. 🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...

  94. 📚 Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...

  95. Check the daily pipeline's state — last run, today's report files, Sonnet quota, recent failures

  96. Trigger the daily digest now (background via OS scheduler) and monitor until completion

  97. Аудит текста на признаки AI без правки (сканер + разбор по скиллу)

  98. Очеловечить русский AI-текст (полное редактирование по скиллу humanizer-ru)

  99. Assess your Claude Code level (0-10) and get a personalized roadmap to the next one

  100. Cancel a running background Antigravity (agy) delegation job.