Menu
Use when fixing bugs, investigating errors, debugging failures, or diagnosing unexpected behavior.
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
Compare Claude Code and Codex on the same real code-change task with isolated worktrees, identical gates, transcripts, time, and cost.
Align AGENTS.md, rules, README, plans, and chronicles with the codebase; use --clean to archive obsolete task docs into ATLAS.md.
Research current best practices and turn the evidence into a clear recommendation. Use for state-of-the-art, evidence-based, optimal-approach, comparison, or pros-and-cons questions in any field.
Clarify an ambiguous or consequential change before planning or implementation when more than one sound approach exists.
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
Create a user-requested Conventional Commit from the staged changes.
| name | debugging |
| description | Use when fixing bugs, investigating errors, debugging failures, or diagnosing unexpected behavior. |
| user-invocable | true |
| allowed-tools | Glob, Grep, Read, Bash, Task, Skill, Edit, Write, AskUserQuestion |
Apply Iron Rules: Principle 9 (root cause, not symptoms) and Principle 8 (every hypothesis tested against fresh evidence) govern every step.
Phase 0 — baseline: run the existing suite first and record pass/fail counts; pre-existing failures are NOT your regressions.
Language context: if a language skill is active, read its patterns.md during investigation for team-specific patterns.
Routing:
/debugging) — announce root cause + proposed fix, then ask before entering the dev workflow.