ワンクリックで
systematic-debugging
Use 4-phase root cause analysis (Observe, Hypothesize, Verify, Fix); avoid unverified patches.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use 4-phase root cause analysis (Observe, Hypothesize, Verify, Fix); avoid unverified patches.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use Git worktrees to create parallel working directories safely; avoid branch-switch contamination.
Behavioral guidelines to reduce common LLM coding mistakes — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.
Enforce "no evidence = no completion"; run Gate Function verification before declaring done.
Pre-ship observability readiness checklist — ensures errors reach production monitoring, not just debug consoles.
Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.
Evaluate when to dispatch parallel agents; use a 4-step pattern to split, coordinate, and integrate results.
| name | systematic-debugging |
| description | Use 4-phase root cause analysis (Observe, Hypothesize, Verify, Fix); avoid unverified patches. |
The core of systematic debugging is: understand first, then fix. When encountering a bug, clarify symptoms, reproduction conditions, and blast radius. Draw hypotheses, verify them with experiments to isolate the root cause, and only then submit a minimal, verifiable fix.