agentsclimarketplace

Run bugfix workflow

Skill lhenrique42/ai-templates/skills/run-bugfix-workflow

Templates for agents, skills, prompts and instructions

Install
npx -y skills add lhenrique42/ai-templates --skill run-bugfix-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Read documented bugs from bugs.md, analyze root causes, implement fixes with regression tests, validate the full test suite, update bug correction status, and generate a final bugfix report. Use when asked to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.

SKILL.md

4.7 KB, as published. Nobody here has run it

Run Bugfix Workflow

Outcome

Execute a complete bugfix cycle from documented issues to validated fixes, including:

  • Prioritized execution from high severity to low severity
  • Root cause analysis per bug
  • Fix implementation and regression tests
  • Full test suite validation
  • Updated correction status in bugs.md
  • Final bugfix report

When to Use

  • User asks to fix bugs
  • User asks to resolve documented issues
  • User asks to run bugfix workflow for a feature area

Do Not Use

  • New feature implementation
  • Code review workflows
  • QA-only testing workflows

Required Inputs

  • bugs.md path or repository context where bugs.md is expected
  • Optional feature scope boundaries
  • Optional runtime/test environment constraints

Workflow

1) Locate and Parse bugs.md

Resolve bug backlog from documented source.

Locate in this order:

  1. User-provided path
  2. bugs.md at repository root
  3. tasks/bugs.md
  4. docs/tasks/bugs.md

Parse fields when present:

  • Bug ID
  • Severity
  • Status
  • Reproduction steps
  • Expected vs actual behavior
  • Existing notes or links

Decision points:

  • If bugs.md is missing, stop and request the exact path.
  • If no open bugs exist, return a no-op completion report.

2) Prioritize and Scope

Create execution queue from high severity to low severity.

Priority order:

  • High
  • Medium
  • Low

Rules:

  • Fix one bug at a time unless coupled root cause is confirmed.
  • Keep fixes within user-confirmed scope.

Decision points:

  • If severity is missing, classify as Medium and flag for confirmation.
  • If bug scope is ambiguous, request clarification before coding.

3) Reproduce and Analyze Root Cause

For each bug in priority order:

  • Reproduce reliably
  • Identify root cause and impacted components
  • Define minimal fix strategy

Decision points:

  • If bug is not reproducible, mark as Blocked - Needs Repro in bugs.md and continue.
  • If root cause suggests cross-cutting risk, add explicit regression scope before implementing.

4) Implement Fixes

Apply code changes per bug with minimal scope.

Implementation rules:

  • Preserve existing architecture and conventions.
  • Avoid opportunistic refactors not required for bug resolution.
  • Keep each bug fix traceable to a bug ID.

Decision points:

  • If fix requires product/spec changes, pause and request approval.
  • If bug is duplicate of an already-fixed issue, cross-reference and mark duplicate status.

5) Add Regression Tests

For each fixed bug, add or update tests that fail before the fix and pass after.

Test expectations:

  • Include targeted regression coverage for the specific failure mode.
  • Include integration/workflow tests when the bug spans component boundaries.

Decision points:

  • If regression test cannot be automated, document manual validation and reason.

6) Validate Full Test Suite

After completing fixes (or after each high-severity fix when risk is high):

  • Run full project test suite
  • Record pass/fail evidence

Decision points:

  • If unrelated pre-existing failures remain, document them separately from bugfix results.
  • If new failures are introduced, treat as blocking and resolve before finalizing.

7) Update bugs.md Status

Update each bug entry using Bug status update template.

Required update fields:

  • Status (Fixed, Blocked - Needs Repro, Duplicate, Deferred)
  • Root cause summary
  • Fix summary
  • Regression test evidence
  • Validation result
  • Last updated date

8) Generate Final Bugfix Report

Create final report using Bugfix report template.

Report includes:

  • Fixed bugs by severity
  • Remaining blocked/deferred bugs
  • Regression and full-suite test outcomes
  • Residual risks and follow-up actions

Quality Check Before Finalizing

Bugfix workflow is complete only if:

  • Bugs were processed in severity priority order.
  • Every fixed bug has root cause notes and regression evidence.
  • Full suite validation result is documented.
  • bugs.md is updated with current correction status.
  • Final bugfix report is generated with clear outcomes.

Output Contract

Return a structured bugfix summary in chat and optionally save markdown artifacts using:

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.