/fix — Fix-and-guard

Fix identified bugs with mandatory regression guard tests.

8|1|Updated Jan 21, 2024

Search Tags:#quality assurance #bug fixing #workflow orchestration #regression testing #test guard #gitmoji commits

Ready to run

npx skills add https://github.com/azigler/dotfiles --skill fix-fix-and-guard

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Typed bug creation: Creates a bug bead with structured problem, symptom, suspected cause, and explicit acceptance criteria so the fix is traceable.
Diagnose-then-fix workflow: Uses a subagent to reproduce, identify the true root cause, and apply the minimum fix without refactoring nearby code.
Mandatory regression guard: Updates an existing relevant test or adds a new regression test so the buggy behavior cannot return unnoticed.

Quick Start

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.

Frequently Asked Questions about /fix — Fix-and-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix bugs and prevent silent regressions at the same time?▼

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.

What is the best way to structure bug fixing for traceable quality assurance?▼

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.

How do I add a regression test when resolving a user-reported defect?▼

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.

Does bug fixing require refactoring nearby code to prevent future issues?▼

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.

When should I use a mandatory regression guard in my workflow orchestration?▼

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.