Run any Skill in Manus with one click

execute-bugfix

Stars0

Forks1

UpdatedMay 21, 2026 at 01:47

Execute bug fixes from documented QA bugs for implemented features. Use when Codex is asked to fix bugs from bugs.md, resolve QA failures, create regression tests, update bugs.md and qa.md, validate fixes with project tests or Playwright MCP, or produce a bugfix report for tasks/prd-[feature-name]/.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rodrigobranas

rodrigobranas/aidev_axon_7

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

6 files

SKILL.md

readonly

name	execute-bugfix
description	Execute bug fixes from documented QA bugs for implemented features. Use when Codex is asked to fix bugs from bugs.md, resolve QA failures, create regression tests, update bugs.md and qa.md, validate fixes with project tests or Playwright MCP, or produce a bugfix report for tasks/prd-[feature-name]/.

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.

More from this repository

same repository

create-prd

rodrigobranas/aidev_axon_7

Create Product Requirements Documents (PRDs) from feature requests using a required clarify-plan-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a PRD, product requirements document, product spec, feature requirements document, or requirements artifact that should be saved as tasks/prd-[feature-name]/prd.md.

2026-05-210

create-tasks

rodrigobranas/aidev_axon_7

Create implementation task lists and individual task files from an existing PRD and Tech Spec. Use when Codex is asked to write, generate, create, draft, or update feature tasks, implementation tasks, task breakdowns, delivery plans, or task files based on tasks/prd-[feature-name]/prd.md and tasks/prd-[feature-name]/techspec.md.

2026-05-210

create-techspec

rodrigobranas/aidev_axon_7

Create implementation-ready Technical Specifications from existing PRDs using a required analyze-research-clarify-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a Tech Spec, technical specification, implementation specification, architecture spec, or engineering plan based on tasks/prd-[feature-name]/prd.md and save it as tasks/prd-[feature-name]/techspec.md.

2026-05-210

execute-bugfix

rodrigobranas/aidev_axon_7

Fix documented QA bugs for a feature by reading bugs.md, qa.md, PRD, Tech Spec, and tasks; planning fixes by severity; implementing root-cause fixes; adding regression tests; validating with project tests and Playwright for UI bugs; and updating bugfix artifacts. Use when Codex is asked to fix bugs, resolve QA findings, address failed QA, or complete bugfix work in tasks/prd-[feature-name]/.

2026-05-210

execute-qa

rodrigobranas/aidev_axon_7

Execute QA validation for a completed feature against its PRD, Tech Spec, and tasks using Playwright MCP, accessibility checks, visual review, bug documentation, and a final QA report. Use when Codex is asked to test, QA, validate, approve, reject, or verify a feature implementation in tasks/prd-[feature-name]/.

2026-05-210

execute-review

rodrigobranas/aidev_axon_7

Execute a code review for implemented work by analyzing git diff, reading modified files, checking project rules and skills, verifying Tech Spec and task adherence, running tests, identifying code quality issues, and saving a code review report. Use when Codex is asked to review code, validate implementation quality, approve changes, or produce codereview.md for a feature or project change.

2026-05-210

name	execute-bugfix
description	Execute bug fixes from documented QA bugs for implemented features. Use when Codex is asked to fix bugs from bugs.md, resolve QA failures, create regression tests, update bugs.md and qa.md, validate fixes with project tests or Playwright MCP, or produce a bugfix report for tasks/prd-[feature-name]/.

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.

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.