systematic-debugging
Systematic Debugging
Never guess at fixes. Find the root cause first.
Phase 1: Understand the Error
- Read the full error message
- Note the exact file, line, error type
- Reproduce the error reliably
- Write: 'The error is: [exact error] at [location] when [trigger].'
Phase 2: Hypothesize
Generate at least 2 hypotheses. For each: what evidence supports it? What would disprove it?
Phase 3: Test Hypotheses
Test each hypothesis with the minimum change to confirm or deny it.
- Add a log line, not a fix
- Test one variable at a time
Phase 4: Fix and Verify
- Write the fix
- Verify the original error is gone
- Verify no new errors
- Add a test that would have caught this bug
More from archieindian/openclaw-superpowers
heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
25context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
25fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
19long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
19agent-self-recovery
Detects when the agent is stuck in a loop and escapes systematically. Use when you notice repeated failures or loss of direction.
18skill-vetting
Reviews a ClawHub skill's source code for security risks before installation. Use before installing any new skill.
18