Guide engineers through five-why root-cause analysis and gated bug-fix workflows.
npx skills add https://github.com/davidmatousek/tachi --skill aod-bugfix
Please help me install this Agent Skill. Skill: ~aod-bugfix Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/~aod-bugfix Command: npx skills add https://github.com/davidmatousek/tachi --skill aod-bugfix
Diagnosing and repairing bugs is often slow and error-prone. This Skill provides a repeatable, five-why based root-cause analysis and a guarded workflow that ensures changes are intentionally applied and documented.
Paste a bug report or failing test output and let the workflow guide you through diagnosis, planning, implementation, verification, and documentation.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis for a failing test is performed using a guided five-why methodology to identify the true cause rather than superficial symptoms. This structured approach ensures accurate diagnosis before proceeding to implementation.
The phase-gate process for a bugfix enforces a non-deferrable confirmation gate before any code edits are applied. It follows a structured workflow: diagnose, plan, implement, verify, and document, ensuring changes are intentional and validated.
Documenting a bugfix for future prevention is handled by automatically generating a knowledge-base entry draft. This creates a post-mortem record from your five-why root-cause statement and verified fix plan for future reference.
Intermittent user-reported bugs can be fixed without missing underlying issues by applying a repeatable five-why root-cause analysis. This workflow ensures you record the true cause and validate the fix plan before implementation.
The best way to prevent superficial fixes when debugging is using a guarded workflow with a confirmation gate before edits. This enforces a structured five-why diagnosis and planning phase to address the true root cause.
saadjsCoordinate a test-first bug-fixing workflow with subagents to propose and verify fixes.
zhukunpenglinyutongApply a five-dimension post-mortem framework to document bug fix root causes.
tsuji-tomonoriAutomate accessibility testing in CI/CD pipelines with quality gates.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
