Skip to content
Get packs

Guide · Agent skill

How to use the GitHub Issue Bugfix Workflow agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The bugfix skill is a set of written instructions that tells an AI coding agent how to fix a bug from a GitHub issue in a fixed order. It is written for the Qwen Code project, so it fits best inside that repository. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what to check before you accept its changes.

GitHub Issue Bugfix WorkflowQwenLM/qwen-code · Apache-2.0

Quick start

  1. 1Install the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings, Capabilities, Skills in the Claude apps.
  2. 2Check the requirements. Confirm that the GitHub CLI is installed and authenticated, that Node.js and npm are available, and that the repo has the npm run build and npm run bundle scripts.
  3. 3Make the request. Ask the agent to fix a bug by giving the GitHub issue URL or number and naming the bugfix workflow.
  4. 4Let it reproduce the bug. The agent saves the issue to a markdown file and the test-engineer agent tries to reproduce the bug before any code changes.
  5. 5Review the fix and verification. Check the fix, the verification report, and the tests the agent added or ran. Do not accept it until verification returns VERIFIED_FIXED.
  6. 6Triage the review. Go through each review comment and mark it as Valid, False positive, or Overthinking, then re-run tests as the skill describes.

What the bugfix skill makes the agent do

An agent skill is a folder with a SKILL.md file that the agent reads when a request matches the skill's description. This one, named bugfix, makes the agent follow a reproduce-first process for GitHub issues. The source says not to skip reproduction, because fixing a bug without first reproducing it tends to give incomplete fixes and regressions.

In order, the agent downloads the issue with the GitHub CLI into a local markdown file, has a separate test-engineer agent reproduce the bug, makes a code fix, rebuilds and has the test engineer verify it, adds or runs tests, then self-audits and reviews the diff.

  • Step 1: read the issue into .qwen/issues/
  • Step 2: reproduce with the test-engineer agent
  • Step 3: fix the code
  • Step 4: build, bundle and verify
  • Step 5: run or add tests
  • Step 6: self-audit and run /review

Install the bugfix skill

Download the ZIP from the skill's page on this directory. Then choose one of these options.

For a personal install, unzip the file into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder. In the Claude apps, you can instead upload the ZIP under Settings, then Capabilities, then Skills.

  • Personal: ~/.claude/skills/
  • Single project: .claude/skills/ inside the project
  • Claude apps: Settings → Capabilities → Skills, then upload

Check the requirements before you start

The skill depends on several things in the environment. Missing any of them will stop the workflow partway through.

The agent runtime needs sub-agents, including a test-engineer agent, and the structured-debugging skill available. You also need the GitHub CLI (gh), authenticated so it can read the issue, plus Node.js and npm. The repository must have the npm run build and npm run bundle scripts, because Step 4 calls them.

  • Qwen Code agent runtime with sub-agents (test-engineer)
  • structured-debugging skill available
  • GitHub CLI (gh), authenticated
  • Node.js and npm
  • npm run build and npm run bundle scripts in the repo
npm run build && npm run bundle

Trigger the skill with a natural request

The skill's description says to use it when you ask the agent to fix a bug, investigate a GitHub issue, or debug a user-reported problem. It takes a GitHub issue URL or number as input. You can also use Qwen Code's slash commands, since their arguments are appended to the skill.

Give the issue number or link and say what you want. Be specific about the outcome, such as reproducing the bug first or fixing it and verifying it.

  • Fix issue 1234 using the bugfix workflow.
  • Investigate https://github.com/owner/repo/issues/1234 and fix the bug.
  • Debug the user-reported problem in issue 1234 and verify the fix.

Understand the safety notes

This skill runs scripts and uses the network. It runs shell commands, writes files and loops on fixes, and it reads issue data from GitHub. The source says the agent should stop and ask the user if it has looped more than 3 times between Steps 3 and 6.

Review the diff yourself before you commit. Check the issue text too, because it comes from users and the agent works from it.

  • Runs shell commands and writes files
  • Downloads issue data over the network via gh
  • Stops to ask you after more than 3 loops between Steps 3 and 6
  • Not suited to unattended fixing of code you have not reviewed

Tips for getting good results

Use the skill for real bugs, not for trivial edits. The skill itself says a plain one-line or trivial config fix can skip the review step, but the rest of the workflow is heavy for small changes.

If the reproduction report says NOT_REPRODUCED, the skill reports that and stops. Treat that as useful information: check the issue details or the environment before asking for another attempt. Triage each review comment as Valid, False positive, or Overthinking, as the skill describes.

  • Use it for bugs in the Qwen Code repository
  • Skip it for one-line or trivial config fixes
  • Read the reproduction and verification reports in the issue file
  • Triage each review comment as Valid, False positive, or Overthinking

What people use it for

  • Contributing a fix for a user-reported crash in the Qwen Code repository with a documented reproduce-first process
  • Triaging a backlog of bug reports where each issue needs a saved reproduction report and verification report
  • Running the test-engineer sub-agent to confirm a bug before a maintainer changes any code
  • Checking an agent's fix against the skill's self-audit and /review steps before opening a pull request

Frequently asked questions

Is the bugfix skill free to use?

The skill is published under the Apache-2.0 licence, as stated on this page. You still need the tools it depends on, such as the GitHub CLI, Node.js and a Qwen Code agent runtime.

What do I need installed to use the bugfix skill?

You need the Qwen Code agent runtime with sub-agents and the structured-debugging skill, the GitHub CLI (gh) authenticated to read the issue, and Node.js and npm. The repo must also have the npm run build and npm run bundle scripts.

Where do I put the bugfix skill files?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps you can upload the ZIP under Settings, Capabilities, Skills.

Can I use the bugfix skill on projects other than Qwen Code?

Not without changes. The skill assumes this repo's npm scripts, dist/cli.js, AGENTS.md and the test-engineer agent, so it would need rewriting for other projects.

Why does the agent stop after saying NOT_REPRODUCED?

The skill's Step 2 says that if the reproduction status is NOT_REPRODUCED, the agent reports that and stops. This prevents fixing a bug that has not been reproduced, which the skill says leads to incomplete fixes and regressions.

How does this compare with asking an agent to fix a bug directly?

The skill adds a fixed order: reproduce first, then fix, then verify with a separate test-engineer agent, then add tests and self-audit. A direct request may skip those steps, while this skill requires them, though it is heavier for small changes.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you contribute to the Qwen Code repository or triage user-reported bugs there and want a repeatable reproduce-first process. Pick something else for quick one-line fixes, for projects other than Qwen Code, or for unattended fixing of code you have not reviewed.

Download the skill