Fix identified bugs with mandatory regression guard tests.
npx skills add https://github.com/azigler/dotfiles --skill fix-fix-and-guard
Please help me install this Agent Skill. Skill: /fix — Fix-and-guard Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/fix Command: npx skills add https://github.com/azigler/dotfiles --skill fix-fix-and-guard
It prevents bugs from silently coming back by requiring every fix to ship with a regression guard (updated or newly added tests) tied to a typed incident bead.
bug bead with structured problem, symptom, suspected cause, and explicit acceptance criteria so the fix is traceable.Run /fix when you learn something is broken, and let the skill create a bug bead, dispatch a fix subagent, and ensure a regression test is added or repaired before closing.
High-intent search queries and answers about installing and using this skill.
To fix bugs and prevent silent regressions, you must pair every code change with a mandatory regression guard test. This ensures the buggy behavior is documented and cannot return unnoticed after the defect is resolved.
The best way to structure bug fixing for quality assurance is creating a typed incident bead with problem context, suspected cause, and explicit acceptance criteria. This makes the fix traceable and enforces a diagnose-then-fix workflow.
To add a regression test when resolving a defect, dispatch a diagnose-and-fix subagent that reproduces the issue, applies the minimum fix, and updates or adds a relevant test before verifying tests and lint pass.
Bug fixing does not require refactoring nearby code to prevent future issues. The workflow focuses on identifying the true root cause and applying the minimum necessary fix without altering surrounding code.
You should use a mandatory regression guard in your workflow orchestration whenever a user-reported defect, reviewer-flagged issue, or orchestrator-detected problem is identified, ensuring tests and lint are verified before merging.
EdanStarfireCreate structured GitHub issues with problem, impact, and acceptance criteria.
fkbertholdCoordinate M1 through M6 stages for bug-shaped bead fixes.
melikhanmutluDiagnose and fix software issues using a 4-phase debugging workflow.
giljaeAutomate web application QA testing, bug detection, and fix verification.