メニュー
Use when the user reports a bug, shows a stack trace, says "something's broken", or asks for help debugging unexpected behavior. Covers reproduction, isolation, root cause, fix, and regression test — the full loop. Applies to any language or stack.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user references or attaches Microsoft Office files (.doc, .docx, .xls, .xlsx, .ppt, .pptx), PDFs, images (.png, .jpg, .jpeg), or CSV/JSON/YAML from Teams or SharePoint and asks to extract, summarize, tabulate, or cross-reference their contents. Ships a runnable `extract.py` — invoke that directly rather than re-implementing extraction inline.
Use when the user asks to integrate a third-party REST or GraphQL API — fetching data, authenticating, handling rate limits, retrying on failure, and wiring responses into the application.
Use when the user asks to add, alter, or drop database tables or columns, create a migration script, or run schema changes safely against a live database.
Use when the user describes a rough feature idea and wants to clarify requirements, resolve open questions, and produce a clean brief before writing a PRD. Activates on phrases like "I want to build", "I have an idea for", "what if we added", "can we make a feature that".
Use when the user asks to produce a PowerPoint deck — presentations, status updates, data read-outs, or structured deliverables. Takes a JSON/YAML spec and writes a .pptx with consistent slide layouts (title, section, bullets, two-column, table). Ships a runnable `generate.py`.
Use when the user asks to produce a formatted Excel workbook — scorecards, data tables, or multi-sheet reports — with consistent styling (headers, number formats, freeze panes, zebra striping). Ships a runnable `generate.py` plus a Python API.
| name | bug-triage-and-debugging |
| description | Use when the user reports a bug, shows a stack trace, says "something's broken", or asks for help debugging unexpected behavior. Covers reproduction, isolation, root cause, fix, and regression test — the full loop. Applies to any language or stack. |
The default workflow for turning a bug report into a landed fix. Bias toward reproducing before theorizing.
../../AGENTS.md
— no tangential cleanup inside a fix PR.| Symptom | Check |
|---|---|
null / undefined / None error | Upstream code that returned it; guard |
| Off-by-one or boundary condition | Loop edges, empty collections |
| Race / non-deterministic | Async ordering, missing await, shared state |
| "Works locally, breaks in prod" | Env differences, missing env vars, versions |
| Recently introduced | git log -p -- <file>; git bisect |
| Silent wrong result | Test coverage gap; assertion is weak |
| Flaky test | Shared state between tests, time, network |
pdb / breakpoint(); pytest -x --pdb on failure;
pytest -k <name> -vv.--inspect-brk + chrome devtools; debugger; statement.delve (dlv debug), go test -run TestFoo -v.lldb / rust-gdb; cargo test -- --nocapture.console.trace() at
suspected call sites.../../AGENTS.md..skip on a failing test. If it's wrong, fix it or delete it —
don't hide it.--no-verify around failing hooks. Fix the hook's complaint.