메뉴
Systematically debug a failing test, error, or unexpected behavior — reproduce, isolate root cause, fix minimally, verify. Use on "debug", "fix this bug", "it's broken", "this is failing", "why is this happening", or a shared error message, stack trace, or failing test output.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write documentation someone will actually read — READMEs, guides, API references, runbooks — short, scannable, example-first, and verified against the code. Trigger on "write docs", "document this", "write a README", "explain how to use this", "our docs are too long/confusing", or a doc that needs rewriting for humans.
Review a diff, branch, or PR for correctness bugs, security issues, and simplification opportunities; findings to docs/<feature-name>/REVIEW.md. Trigger on "review this", "code review", "security review", "audit this", or after something is implemented and needs checking before merge.
Write docs/<feature-name>/PLAN.md with phased, checkbox-driven steps for a feature, refactor, upgrade, or infrastructure change. Trigger on "create/make a plan", "plan this feature/refactor/upgrade", any request to document steps before coding, and proactively when complexity warrants a written plan.
Decide a feature's shape before planning — system design, data model, API contract, UI/UX, whichever apply — and write docs/<feature-name>/DESIGN.md. Trigger on "design this feature/API/schema/UI", "how should we structure this", or between dev-research and dev-create-plan.
Execute an implementation plan from docs/<feature-name>/PLAN.md — tick checkboxes, commit each phase. Trigger on "implement/execute/continue/resume the plan", "start phase 1", "go" right after a plan was created, or whenever there is a PLAN.md to build, even if the user never says "plan".
Run an autonomous plan → implement → review loop for a feature, iterating until the code review passes and pausing for approval before pushing. Use on "loop on this", "keep going until it passes review", "autonomous dev loop", "plan implement and review", or a self-correcting agent workflow.
| name | dev-debug |
| description | Systematically debug a failing test, error, or unexpected behavior — reproduce, isolate root cause, fix minimally, verify. Use on "debug", "fix this bug", "it's broken", "this is failing", "why is this happening", or a shared error message, stack trace, or failing test output. |
| argument-hint | [lite|full|ultra] |
Reproduce → isolate → fix → verify. Never guess at a fix before reproducing.
lite | full | ultra, default lite)Mode is the trailing argument when it is exactly lite, full, or ultra; everything else is the task/feature description. No mode given → lite.
lite (default) — one commit: test + fix together.full — regression test committed separately before the fix (cause visible in history).ultra — reproduce and fix in an isolated worktree when the bug touches shared/risky state; merge once verified.Get a reliable reproduction before touching code. Can't reproduce → stop, ask for environment/input/frequency. A fix you can't verify is a guess.
Work from symptom inward — don't fix the first suspicious thing:
git log --oneline -20, git bisect if needed.State it before fixing: "Root cause: <what> because <why>."
Change only what the root cause requires. No adjacent refactoring/renames — that's a dev-refactor session. If the real fix needs structural change, note it and fix the symptom for now.
Re-run the reproduction (must pass) and the full suite (must not regress). New failures your fix introduced → address before committing.
If no test caught this bug, add one that would have. Not feasible (no suite, integration-only) → note why.
Commit hygiene and message style: see the git-safe skill (no Co-authored-by:, git add -u not -A, imperative why-focused subject).
lite: git add <test file> && git add -u && git commit -m "fix: <root cause> (with regression test)".
full: git commit -m "test: reproduce <bug>" first, then git commit -m "fix: <root cause>".
Bug (one line) · root cause · fix (what and why) · verified by (test/command) · regression test (added | n/a — reason).