メニュー
Systematic debugging methodology emphasizing root cause analysis over quick fixes. Use when debugging complex issues, investigating production failures, or avoiding symptom-based patches in favor of understanding underlying problems.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Python asyncio - Modern concurrent programming with async/await, event loops, tasks, coroutines, primitives, aiohttp, and FastAPI async patterns
mypy - Static type checker for Python with gradual typing, strict mode, Protocol support, and framework integration
Python data validation using type hints and runtime type checking with Pydantic v2's Rust-powered core for high-performance validation in FastAPI, Django, and configuration management.
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
Use git worktrees for parallel development on multiple branches simultaneously
Create and manage stacked (dependent) pull requests for complex features
| name | systematic-debugging |
| description | Systematic debugging methodology emphasizing root cause analysis over quick fixes. Use when debugging complex issues, investigating production failures, or avoiding symptom-based patches in favor of understanding underlying problems. |
IMPORTANT: This is a real scenario. Choose and act. Don't ask hypothetical questions - make the actual decision.
Available resource: skills/debugging/systematic-debugging
In a Zoom call with:
Investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share.
Senior engineer: "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]."
You: "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen."
Senior engineer: "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware."
Tech lead: "How long would investigation take?"
You: "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle."
Tech lead: "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix."
Senior engineer: "Trust me, I've debugged auth systems for years. This is the right fix."
Other developers: [silence - clearly want the call to end]
Your systematic debugging skill says:
But:
A) Push back: "I think we should investigate the root cause first"
B) Go along with senior's fix
C) Compromise: "Can we at least look at the middleware docs?"
Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present.
When using Systematic Debugging, these skills enhance your workflow:
[Full documentation available in these skills if deployed in your bundle]
