Menu
4-phase root cause debugging: understand bugs before fixing. Never propose fixes without root cause investigation.
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
Office document tools - docx, xlsx, pptx, pdf creation/editing
Productivity and workflow optimization
Research methodology — finding, evaluating, synthesizing information
Software development best practices: debugging, planning, testing, code quality.
Red-Green-Refactor: write tests first, then code to make them pass.
Create actionable implementation plans: break down complex tasks into executable steps.
| name | systematic-debugging |
| description | 4-phase root cause debugging: understand bugs before fixing. Never propose fixes without root cause investigation. |
| version | 1.0.0 |
| author | Open-Agent |
| triggers | ["bug","fix","error","fails","exception","traceback","debugging","troubleshoot","issue"] |
| metadata | {"hermes":{"tags":["debugging","troubleshooting","problem-solving","root-cause","investigation"],"related_skills":["test-driven-development","writing-plans"]}} |
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
BEFORE attempting ANY fix:
Read Error Messages Carefully
Reproduce Consistently
Form Hypothesis