Systematic Debugging
SkillDev toolsUse when diagnosing a failure, flaky behavior, or unexpected output before attempting a fix.
Then ask your AI: use the Systematic Debugging skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
What this skill tells your AI
The instructions your AI receives, as published by rakuensoftware/aimee in skills/systematic-debugging/SKILL.md and read by Ahel’s review.
Start with evidence, not guesses.
- Reproduce the failure with the smallest command, input, or trace available.
- Read the failing path until you can explain where expected state diverges from actual state.
- Form one hypothesis that predicts an observable result.
- Test the hypothesis with a targeted command, log, assertion, or code read.
- Apply a fix only after the evidence identifies the cause.
After three failed fixes, stop changing code and re-check the model of the system. Repeated patches without a new observation usually mean the cause is elsewhere.
Useful references:
references/root-cause-tracing.mdreferences/condition-based-waiting.md
Signals
- GitHub stars
- 187
- Forks
- 69
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
systematic-debugging-rakuensoftware- Source
- github.com/rakuensoftware/aimee
github.com/rakuensoftware/aimee