Systematic Debugging — 4-phase root cause debugging: understand bugs before fixing
Systematic Debugging — 4-phase root cause debugging: understand bugs before fixing
Start with meaning, then move to detail.
This lesson explains Systematic Debugging — 4-phase root cause debugging: understand bugs before fixing as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Overview, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Systematic Debugging — 4-phase root cause debugging: understand bugs before fixing without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
4-phase root cause debugging: understand bugs before fixing
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Overview
Read this after the foundation, then connect it to the previous step.
- 04The Iron Law
Read this after the foundation, then connect it to the previous step.
- 05The Feedback Loop Rule
Read this after the foundation, then connect it to the previous step.
- 06When to Use
Read this after the foundation, then connect it to the previous step.
- 07The Four Phases
Read this after the foundation, then connect it to the previous step.
- 08Phase 1: Root Cause Investigation
Read this after the foundation, then connect it to the previous step.
- 091. Read Error Messages Carefully
Read this after the foundation, then connect it to the previous step.
- 102. Build a Tight Feedback Loop
Finish here to verify the result and special cases.
Copy only after you understand the effect.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST# Run a specific failing test
pytest tests/test_module.py::test_name -v
# Or run a scripted repro
python scripts/repro_bug.py
# Or run a high-repetition flaky repro
for i in {1..100}; do pytest tests/test_flake.py::test_name -q || break; done# Recent commits
git log --oneline -10
# Uncommitted changes
git diff
# Changes in specific file
git log -p --follow src/problematic_file.py | head -100Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.