Menú
Systematic debugging with hypothesis-driven investigation. Use when: "debug", "not working", "bug", "broken", "error", "unexpected behavior", "fix issue", "investigate"
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Full codebase audit: architecture health, dependencies, complexity, tech debt. Use when: "audit", "health check", "codebase analysis", "tech debt", "architecture review", "dependency check", "code quality"
Structured brainstorming with multiple approaches and tradeoffs. Use when: "brainstorm", "explore options", "what are my options", "compare approaches", "pros and cons", "which is better", "how should I", "alternatives"
Build error diagnosis and resolution. Use when: "build failed", "compile error", "bundler error", "fix build", "npm error", "type error", "won't compile"
Scaffold a new application with interactive dialogue. Use when: "create", "build me", "make an app", "new project", "scaffold", "generate app", "start new"
Generate a new custom skill from natural language description. Use when: "create skill", "new skill", "make a skill", "add command", "custom workflow", "skill template", "generate skill"
Production deployment with pre-flight checks and verification. Use when: "deploy", "ship", "release", "go live", "push to prod", "publish", "launch"
| name | debug |
| description | Systematic debugging with hypothesis-driven investigation. Use when: "debug", "not working", "bug", "broken", "error", "unexpected behavior", "fix issue", "investigate" |
| argument-hint | <issue description> |
| user-invocable | true |
| disable-model-invocation | true |
$ARGUMENTS
This command activates DEBUG mode for systematic investigation of issues, errors, or unexpected behavior.
When /debug is triggered:
Gather information
Form hypotheses
Investigate systematically
Fix and prevent
## 🔍 Debug: [Issue]
### 1. Symptom
[What's happening]
### 2. Information Gathered
- Error: `[error message]`
- File: `[filepath]`
- Line: [line number]
### 3. Hypotheses
1. ❓ [Most likely cause]
2. ❓ [Second possibility]
3. ❓ [Less likely cause]
### 4. Investigation
**Testing hypothesis 1:**
[What I checked] → [Result]
**Testing hypothesis 2:**
[What I checked] → [Result]
### 5. Root Cause
🎯 **[Explanation of why this happened]**
### 6. Fix
```[language]
// Before
[broken code]
// After
[fixed code]
🛡️ [How to prevent this in the future]
---
## Examples
/debug login not working /debug API returns 500 /debug form doesn't submit /debug data not saving
---
## Key Principles
- **Ask before assuming** - get full error context
- **Test hypotheses** - don't guess randomly
- **Explain why** - not just what to fix
- **Prevent recurrence** - add tests, validation