Investigate root causes through a 4-phase process before modifying code.
npx skills add https://github.com/hicucu/forge --skill systematic-debugging-hicucu
Please help me install this Agent Skill. Skill: systematic-debugging Source: https://github.com/hicucu/forge/tree/main/skills/systematic-debugging Command: npx skills add https://github.com/hicucu/forge --skill systematic-debugging-hicucu
Random fixes waste time and create new bugs. Quick patches hide root causes, leading to recurring issues and technical debt. This skill enforces a disciplined 4-phase process to ensure you always identify and fix the true source of problems, even under extreme time pressure, authority bias, or sunk cost fallacies.
Use the systematic-debugging skill to investigate the failing payment processing test by starting with Phase 1 root cause analysis before attempting any fix.
High-intent search queries and answers about installing and using this skill.
Systematic debugging enforces a 4-phase process—investigation, pattern analysis, hypothesis, and implementation—to identify the root cause of test failures before proposing any modifications. This eliminates symptom-fixing and prevents recurring bugs.
Debugging a production outage under time pressure requires a pressure-resistant process that enforces single-hypothesis validation and mandatory architectural review after three failed fix attempts. This prevents deploying risky retry patches without understanding the true failure mode.
Bug fixes repeatedly failing indicate skipped root cause analysis. A systematic debugging process mandates a strict architectural review after three failed fix attempts, forcing re-analysis of the underlying patterns instead of continuing ineffective patches.
Handling flaky tests and unexpected integration behavior requires condition-based waiting and defense-in-depth validation across all layers. These techniques isolate the true failure mode by tracing deep stack traces instead of applying quick patches.
A systematic debugging process should not be used when a fast, temporary symptom patch is explicitly required for immediate mitigation and the technical debt is accepted. Its strict 4-phase root cause investigation and anti-shortcut rules add latency unsuitable for non-critical, trivial fixes.
FoundationForgeRun structured debugging sessions to reproduce, isolate, and diagnose software errors.
aist-ai-sastDiagnose MCP regression failures and implement durable fixes across test suites.
timequityReplace arbitrary delays with condition-based waiting in JavaScript/TypeScript test suites.
htlin222Search and analyze log files and codebases for error patterns and stack traces.
