Skip to main content
ClaudeWave

Slash Commands de Claude Code · página 10

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. Diagnose a failing Cloud Run service — Antigravity (agy/Gemini) digests the error logs cheaply, Claude infers the root cause and proposes a fix. Read-only by default; --apply writes the fix to a branch.

  2. Delegate a well-scoped subtask to Antigravity (agy/Gemini) under cost discipline, then verify.

  3. Understand an audio / video / image file — Antigravity (agy/Gemini) transcribes and analyzes it, returning a timestamped digest while the full transcript goes to a file.

  4. Migrate an existing Claude Code setup (skills, memory, CLAUDE.md, MCP, plugins, permissions) to the Antigravity CLI.

  5. Claude-orchestrated deep research — Antigravity (agy/Gemini) does the grounded web legwork; Claude plans, verifies the citations, and synthesizes.

  6. Fetch the output of a finished background Antigravity (agy) job, then verify it.

  7. Get an independent cross-model review of the current diff from Antigravity (Gemini), then reconcile as the final judge.

  8. Verify the Antigravity (agy) CLI is installed and authenticated and the plugin is ready to use.

  9. List background Antigravity (agy) delegation jobs for this repo, or show one job's status.

  10. |

  11. Launch the API documentation specialist for OpenAPI specs

  12. api277

    Launch the API development agent for backend implementation

  13. Alternative command for content creation

  14. Debug an error or issue

  15. Alternative command for DevOps deployment tasks

  16. Launch the DevOps specialist for CI/CD and deployment

  17. Generate or update documentation

  18. Launch the frontend development agent for UI implementation

  19. Launch the marketing content specialist

  20. plan277

    Launch the project planning agent for strategic task decomposition

  21. Launch the product management specialist

  22. Refactor code for better structure and maintainability

  23. Alternative command for requirements gathering

  24. Trigger code review on recent changes

  25. Scan for security vulnerabilities

  26. Launch the ShadCN UI builder agent for component-based UI development

  27. tdd277

    Launch the TDD specialist for test-driven development

  28. Alternative command for TDD specialist focusing on test-first approach

  29. test277

    Run tests and fix failures

  30. ui277

    Launch the ShadCN UI builder agent for interface design and implementation

  31. Initialize Beads issue tracking in your project with interactive configuration setup.

  32. Dead code detection and cleanup workflow (inline orchestration)

  33. Dependency audit and update workflow (inline orchestration)

  34. Code duplication detection and consolidation workflow (inline orchestration)

  35. Security vulnerability detection and remediation workflow (inline orchestration)

  36. Connect any project to Gastown multi-agent orchestration

  37. push249

    Automated release management with version bumping and dual changelog generation

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

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

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

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

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

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

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

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

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

  47. Import tasks from tasks.md into Beads issue tracker, creating an epic with child tasks and proper dependencies.

  48. Show Gastown status (convoys, agents, pending tasks)

  49. Optimize Supabase database performance by delegating to specialized agents

  50. Translate documentation file from English to Russian

  51. Deep analysis and problem solving with multi-dimensional thinking

  52. Safely upgrade Gastown and Beads

  53. work249

    Give task to AI agent via Gastown (create bead + sling to polecat)

  54. Manage git worktrees for parallel feature development (create, remove, list, cleanup)

  55. WordPress performance code review - detects database anti-patterns, caching issues, hook problems, and scalability concerns

  56. Quick WordPress performance scan - fast triage using critical pattern detection

  57. Build the colcon workspace (optionally a single package) and report the outcome.

  58. Summarize commits on the current branch (vs origin/main) into a Changelog-style bullet list ready to paste into Changelog.md.

  59. Run pre-commit hooks (clang-format, codespell, etc.) over the staged + changed files, then optionally clang-tidy.

  60. Scaffold a new ECS component header under include/gz/sim/components/ and wire it into the install list.

  61. Scaffold a new gz-sim system plugin under src/systems/<name>/ with header, source, CMake glue, plugin registration, and an integration test stub.

  62. Run the gz-sim CTest suite (optionally filtered by regex) and report pass / fail counts.

  63. lint214

    Run ament linters (uncrustify, cpplint, flake8, pep257, xmllint, copyright) and pre-commit against changed files.

  64. Author a new sub-agent under .claude/agents/<name>.md with valid frontmatter (name/description/tools/model), following the template conventions, and index it in CLAUDE.md + README.md.

  65. Scaffold a Behavior Tree leaf node — plain BehaviorTree.CPP (sync/stateful/condition) or a BehaviorTree.ROS2 wrapper (action/service/topic) — with ports, registration, and an XML usage snippet.

  66. Author a new slash command under .claude/commands/<name>.md with valid frontmatter, following the template conventions, and index it in CLAUDE.md + README.md.

  67. Scaffold a ros2_control controller or broadcaster — base class, command/state interface config, RT-safe update(), generate_parameter_library, pluginlib export, and a test.

  68. Scaffold a ros2_control hardware component (System/Actuator/Sensor) + URDF <ros2_control> tag + bringup (controllers.yaml + launch), with pluginlib export and a test.

  69. Scaffold a modular launch file (Python or XML) inside an existing package, following the ros2_launch_config skill.

  70. Scaffold a Node inside an existing package — standard, lifecycle, or component, in Python or C++.

  71. Scaffold a new ROS 2 package (ament_python or ament_cmake) following Clean Architecture layout — domain / application / infrastructure / presentation.

  72. Scaffold a Clean-Architecture VDA 5050 v3.0.0 connector (MQTT/JSON ↔ Nav 2) — domain entities, ports, application handlers, MQTT + Nav 2 adapters — in the chosen code format.

  73. Bootstrap a complete ROS 2 colcon workspace from scratch — dir layout, .gitignore, README, this .claude/ config, and seed interfaces/core/bringup packages.

  74. test214

    Run colcon tests for the workspace (or a single package) and report pass / fail counts.

  75. Product Manager-led orchestration with optional thinking modes, MCP servers, and flexible input types (request/PRD/PRP)

  76. Run cc-fleet's setup/health diagnostics and explain any failures (read-only)

  77. ps212

    List cc-fleet provider teammates, async jobs, and pane health (read-only)

  78. Analyze and optimize context configuration. Reviews CLAUDE.md, knowledge-core.md, and active context for optimization opportunities. Helps prevent context rot (39% improvement, 84% token reduction).

  79. Quick command to invoke code-implementer to execute implementation with self-correction (up to 3 intelligent retries).

  80. plan207

    Quick command to invoke implementation-planner to create surgical, reversible implementation plans with rollback procedures.

  81. Quick command to invoke docs-researcher for rapid documentation research. Fetches version-accurate, authoritative sources and creates ResearchPack.

  82. Complete Research → Plan → Implement workflow in one command. Invokes chief-architect to orchestrate all phases with quality gates and self-correction.

  83. Advance the current Writ workflow phase with an explicit tool-confirmed advance. NOT a replacement for pattern-match approval detection; this command spends the token that detection mints (see Authorization below).

    infinri/WritInstalar
  84. Install pitchcraft skill for structured persuasion and executive reporting

  85. 安装 pitchcraft skill(结构化说服与汇报)

  86. Build from the plan

  87. Onboard Claude Code into the codebase

  88. Load Obsidian plugin development guidelines and best practices

  89. Interactive guide for creating a new Obsidian plugin with best practices

  90. init161

    Generate FILETREE.md from scratch. Confirms overwrite if it already exists.

  91. lint161

    Report drift between FILETREE.md and current repo, read-only. Prompts to run /filetree:update on drift.

  92. Sync FILETREE.md with current repository state — handles added / changed / removed / renamed.

  93. Force recalibration of all CLAUDE.md files

  94. init158

    Initialize CLAUDE.md memory structure for project with interactive wizard

  95. Show CLAUDE.md memory sync status

  96. sync158

    Sync CLAUDE.md with manual file changes detected by git

  97. Activate Nemp Pro with your license key

  98. View captured activity log

  99. Enable or disable automatic activity capture

  100. Enable or disable automatic cross-provider memory export