rodrigobranas/aidev_axon_7/execute-bugfix

Execute Bugfix

Core Workflow

Use this skill to fix all documented bugs for a feature, add regression coverage, validate the project, and update QA artifacts.

Read resources/execute-bugfix.md before starting. Treat that file as the canonical workflow for this skill.

Load resources/bugfix-plan-template.md when producing the per-bug fix planning summary. Load resources/bug-status-update-template.md when updating fixed bug entries in bugs.md. Load resources/bugfix-report-template.md only when generating the final bugfix report. Treat these files as the required template standards.

Execution Rules

• Confirm and read bugs.md, qa.md, prd.md, techspec.md, and tasks.md under tasks/prd-[feature-name]/.
• Review project rules and relevant project skills before editing.
• Use Context7 MCP for documentation of involved languages, frameworks, and libraries when relevant.
• Plan each bug fix using resources/bugfix-plan-template.md.
• Fix bugs in severity order: High, then Medium, then Low.
• Fix root causes, not superficial symptoms or workarounds.
• Create regression tests for every fixed bug.
• Use Playwright MCP for visual or frontend bug validation.
• Run the full relevant test suite and type checking.
• Update each fixed bug in bugs.md using resources/bug-status-update-template.md.
• Update qa.md so bug status, verification details, evidence, and test counts remain consistent.
• Generate the final report from resources/bugfix-report-template.md.

Expected Inputs

Typical input is a feature directory, feature name, bug report path, or request such as:

• "Use $execute-bugfix for tasks/prd-team-invitations."
• "Fix all bugs in tasks/prd-checkout-flow/bugs.md."
• "Resolve the QA failures and update bugs.md and qa.md."

If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible feature folders exist.