--- name: bugfix-06d9ce6ee6aa 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, `` 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 \ --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-.md ``` ## Step 2: Reproduce Spawn the `test-engineer` agent and point it at ``. 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 `` 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. --- Source attribution: QwenLM Original project: https://github.com/QwenLM/qwen-code License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 Gabriel Moreira Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: QwenLM Original project: https://github.com/QwenLM/qwen-code Attribution basis: Upstream repository explicitly recorded in package mirror path Fields of work: Development & Engineering Roles: Backend Developer, DevOps / SRE, QA / Test Engineer Specialties: Backend, Testing Tools: GitHub Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 9255c751038bbde49aede73b14e33ccdc89c8accabc3de4aa52034d41a123b45