
Systematic Debugging
This is the disciplined alternative to guessing at fixes. It forces you to drill upward through diagnostic layers (symptom, logic, system, architecture, contracts, platform, spec gaps) until you hit root cause, then runs triage checks before you touch code. The patch-shape triage alone is worth it: it catches those tempting "just add a guard" fixes that turn into technical debt because you patched the consumer instead of fixing the canonical owner. Use it when you're under pressure and want to skip investigation, when you've already tried two fixes that didn't work, or anytime fallback chains and duplicate owners are in play. The quality gates feel heavy at first but they prevent the expensive kind of bug whack-a-mole.
- GitHub stars
- 492
- last updated
- Jun 11, 2026
Install
$ npx -y skills add ganyuanran/aegis --skill systematic-debugging --agent claude-codeInstalls into .claude/skills of the current project.
Files
Sponsors
Details
- Repository
- github.com/ganyuanran/aegis
- Category
- Debugging
- License
- MIT
- First seen
- Jun 11, 2026
More from ganyuanran/aegis
All 22- Test Driven Development
- Update Aegis
- Using Aegis
- Using Git Worktrees
- Verification Before Completion
- Writing Plans
- Writing Skills
- Anti Entropy Governance
- Brainstorming
- Communicating Concisely
- Dispatching Parallel Agents
- Establishing Project Context
- Executing Plans
- Finishing A Development Branch
- First Principles Review
- Goal Framing
- Long Task Continuation
- Receiving Code Review
- Recording Architecture Decisions
- Requesting Code Review
- Subagent Driven Development