Menu
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when doing any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a written implementation plan to execute with review checkpoints
Use when implementation is complete and all tests pass — guides completion by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions — requires technical rigor and verification, not performative agreement
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
| name | nobody-debugs |
| description | Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes |
4-phase process: reproduce, isolate, identify root cause, fix with test.
Core principle: Random fixes waste hours. Systematic tracing takes minutes.
Announce at start: "I'm using the nobody-debugs skill to trace this."
Before anything else, get a reliable reproduction:
Cannot reproduce? Gather more data before proceeding. Don't guess.
Narrow down where the problem lives:
Goal: "The bug is in function X, triggered when Y happens."
Trace backward from the symptom to the origin:
Root cause checklist:
Common traps:
| Problem | Action |
|---|---|
| Can't reproduce | Add logging, try different environments |
| Too many variables | Isolate one variable at a time |
| Fix broke something else | Revert, understand dependencies first |
| "No root cause found" | 95% of the time = incomplete investigation |
