Menu
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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
| name | systematic-debugging |
| description | Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. |
| type | skill |
| version | 1.0.0 |
| category | verification |
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Prevents "guessing" and ensures scientific investigation.
The systematic debugging process consists of four distinct phases of investigation and implementation.
git diff is your best friend.Follow these best practices to maintain a rigorous debugging standard.
If 3+ fixes have failed: STOP.
Automated governance, hook installation, pre-commit validation, branch isolation, and safe commit operations.
Enforcement of safety guardrails, axiom verification, secret scanning, and mutability protections.
Building and managing premium statistical dashboards, RAG explorer UIs, warehouse log monitors, and real-time visualization centers.
Integration of agent systems with blockchain protocols, contracts, event stores, reputation networks, and collective verification engines.
AI model configuration, LLM memoization, agentic RAG search, and vector library maintenance.
Catalog generation, reference link verification, workshop documentation building, and knowledge gap analysis.