bugfix
/bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
- Author
- qwenlm ↗
- Repository
- qwen-code ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
Original author description
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
How it works
- Input
- Artifact Path
- Step 1: Read The Issue
- Step 2: Reproduce
- Step 3: Fix
- Step 4: Verify
- Step 5: Tests
- Step 6: Self-Audit and Code Review
- Iteration Rules
SKILL.md preview
---
name: bugfix
description: Fix a bug from a GitHub issue, following the reproduce-first
workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or
debug a user-reported problem. Takes a GitHub issue URL or number as input.
---
# Bugfix Workflow
Follow this workflow for GitHub issue bugfixes. Do not skip reproduction; fixing
without first reproducing the bug tends to produce incomplete fixes and
regressions.
## Input
A GitHub issue URL or number. Slash-command arguments are appended to this skill
body by Qwen Code.
## Artifact Path
Use `.qwen/issues/` in this repo. In the steps below, `<issue-file>` means the
selected issue markdown file.
## Step 1: Read The Issue
Create the artifact directory if needed, then pipe the issue directly into a
markdown file using `gh`:
```bash
mkdir -p .qwen/issues
gh issue view <number> \
--json number,title,body \
-t '# Issue #{{.number}}: {{.title}}
{{.body}}
---
## Reproduction report
_Pending - to be filled by the test engineer._
## Verification report
_Pending - to be filled by the test engineer._
' > .qwen/issues/issue-<number>.md
```
## Step 2: Reproduce
Spawn the `test-engineer` agent and point it at `<issue-file>`. State only the
goal: reproduce the bug. Keep the prompt minimal; the test engineer owns the
reproduction strategy.
Wait for the test engineer to finish. Then read `<issue-file>` to get the
reproduction report. If the status is `NOT_REPRODUCED`, report that and stop.
## Step 3: Fix
Read the relevant code and make the fix. Use the reproduction report for
context; it should contain observed behavior, expected behavior, and useful code
paths.
If the bug is complex enough that the first attempt does not work, use the
`structured-debugging` skill and work through hypotheses systematically.
## Step 4: Verify
Build and bundle your changes:
```bash
npm run build && npm run bundle
```
Spawn the `test-engineer` agent again, pointing it at the same issue file. State
the goal: verify the fix using `node dist/cli.js`.
If the verification status is `STILL_BROKEN`, read the updated issue file, go
back to Step 3, and iterate. Do not proceed until verification returns
`VERIFIED_FIXED`.
## Step 5: Tests
Run unit tests for any packages you modified. If the test engineer wrote a
failing test during reproduction, make sure it passes after the fix. Otherwise,
add focused regression coverage for the failure scenario.
## Step 6: Self-Audit and Code Review
First self-audit the full diff per the self-audit step in AGENTS.md's General
workflow (open-ended passes plus presume-wrong verification, until two
consecutive clean passes; one clean pass suffices for a trivial fix). If the
audit changes source, re-run Step 4 before resuming it. Skip the review below
only for a plain one-line or trivial config fix. For anything else, run
`/review` with a review task listing all changed files. Triage each comment
with a verdict:
- **Valid**: real bug or meaningful improvement. Fix it.
- **False positive**: reviewer missed context. Skip it.
- **Overthinking**: technically plausible but not worth the complexity. Skip
it.
After fixing valid issues, re-run unit tests and a quick verification sanity
check.
## Iteration Rules
- If Step 4 fails, go back to Step 3, then re-run Step 4.
- If Step 6 finds valid issues, fix them, re-run Step 4 as a sanity check,
and re-run the self-audit.
- Do not loop more than 3 times between Steps 3-6 without asking the user.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · qwenlm/qwen-code | 100 | Apache-2.0 |
| grimoire-rs/grimoire | 100 | Apache-2.0 |
| marian-kamenistak/sap-ai-skills | 100 | MIT |
| duthaho/skillhub | 100 | MIT |
| alibaba/mnn | 95 | Apache-2.0 |
| 4typen/skills | 90 | MIT |
| kangig94/coral | 90 | MIT |
| woliveiras/baseline | 86 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 093862583abc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100fix-bug
Fix a reported bug in React Router from a GitHub issue. Use when the user provides a GitHub issue URL and asks to fix a bug, investigate an issue, or reproduce a problem. Handles the full workflow: fetching the issue, finding the reproduction, writing a failing test, and implementing the fix. - 100reproduce-bug
Systematically reproduce and investigate a bug from a GitHub issue. Use when the user provides a GitHub issue number or URL for a bug they want reproduced or investigated. - 100reproduce-bug
Systematically reproduce and investigate a bug from a GitHub issue. Use when the user provides a GitHub issue number or URL for a bug they want reproduced or investigated. - 100fix-bug
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix #123", GitHub issue URLs, or any request to resolve a reported problem from a GitHub issue. Also triggers when asked to investigate errors, diagnose failures,… - 100reproduce-bug
Systematically reproduce and investigate a bug from a GitHub issue. Use when the user provides a GitHub issue number or URL for a bug they want reproduced or investigated. - 100implementing-bug-fix
Implements a bug fix from a GitHub issue URL or ID, or auto-selects the next feasible confirmed P0-P3 bug. Researches and reproduces the bug, plans, implements, tests, and creates a merge-ready PR. Use when asked to fix a bug, implement a bugfix, or run /implementing-bug-fix.