Agent skill

GitHub Issue Bugfix Workflow

Fixes a bug from a GitHub issue by reproducing it first with a test-engineer subagent, then fixing, verifying, adding regression tests and reviewing the diff.

Apache-2.0Auto-check passedDevelopment

Install GitHub Issue Bugfix Workflow

skills CLI

$ npx skills add QwenLM/qwen-code --skill bugfix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install QwenLM/qwen-code bugfix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.qwen/skills/bugfix .claude/skills/bugfix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "bugfix" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix into .claude/skills/bugfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bugfix", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add QwenLM/qwen-code --skill bugfix -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install QwenLM/qwen-code bugfix --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.qwen/skills/bugfix .agents/skills/bugfix && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bugfix" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix into .agents/skills/bugfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bugfix", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add QwenLM/qwen-code --skill bugfix -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install QwenLM/qwen-code bugfix --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.qwen/skills/bugfix .cursor/skills/bugfix && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bugfix" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix into .cursor/skills/bugfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bugfix", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/QwenLM/qwen-code.git --path .qwen/skills/bugfix

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add QwenLM/qwen-code --skill bugfix -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install QwenLM/qwen-code bugfix --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.qwen/skills/bugfix .gemini/skills/bugfix && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "bugfix" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix into .gemini/skills/bugfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bugfix", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install QwenLM/qwen-code bugfix

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add QwenLM/qwen-code --skill bugfix -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.qwen/skills/bugfix .github/skills/bugfix && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "bugfix" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix into .github/skills/bugfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bugfix", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add QwenLM/qwen-code --skill bugfix -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install QwenLM/qwen-code bugfix --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.qwen/skills/bugfix .opencode/skills/bugfix && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bugfix" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/bugfix into .opencode/skills/bugfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bugfix", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: bugfix
GitHub stars: 28k
Token cost: ~873 tokens
SKILL.md length: 445 words
Files: 1
Skills in repo: 41
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Fixes a bug from a GitHub issue by reproducing it first with a test-engineer subagent, then fixing, verifying, adding regression tests and reviewing the diff.

Works in 6 steps: Read The Issue → Reproduce → Fix → …
Fixing a bug reported in a GitHub issue in the Qwen Code repository
SKILL.md covers Input, Artifact Path, Step 1: Read The Issue and Step 2: Reproduce, plus 5 more sections
Calls npm, gh and node

What it does

The skill takes a GitHub issue URL or number and insists on reproduction before any fix, since fixing without a reproduction tends to give incomplete fixes and regressions. It saves the issue as a markdown file under .qwen/issues/ using the gh CLI, then spawns a test-engineer agent whose only goal is to reproduce the bug and write a report. If the report says NOT_REPRODUCED, the work stops there.

The agent then reads the relevant code and applies the fix, switching to the structured-debugging skill when the first attempt fails. Verification builds the project with npm run build and npm run bundle, and the test engineer checks the fix again with node dist/cli.js. The loop repeats until the status is VERIFIED_FIXED, after which unit tests run for the changed packages and a regression test is added if none exists.

The last step is a self-audit of the full diff, repeated until two consecutive passes find nothing, followed by a /review run over the changed files unless the fix is trivial. Commands and paths are specific to the Qwen Code repository.

When your agent uses it

Fixing a bug reported in a GitHub issue in the Qwen Code repository
Investigating a user-reported problem where the failure must be reproduced first
Adding regression coverage and a review pass after a bug fix

Example prompts

“Fix the bug described in GitHub issue 7, reproducing it first.”
“Investigate this issue URL and tell me whether the bug reproduces before changing code.”
“Run the bugfix workflow on the crash reported in issue 3.”

Requirements

The gh CLI, authenticated for the repository
Node.js and npm for the build and bundle steps
A test-engineer subagent

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Read The Issue
Reproduce
Fix
Verify
Tests
Self-Audit and Code Review

What it can do on your machine

Read from SKILL.md and the folder at commit 4970bfa. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npm
- gh
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Issue Bugfix Workflow loads about 873 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 445 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~873

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from QwenLM/qwen-code at commit 4970bfa, republished under its Apache-2.0 licence (© QwenLM). 445 words, ~873 tokens.

Download SKILL.mdSave it as .claude/skills/bugfix/SKILL.md (or your agent's skills folder).

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.

Show full SKILL.md (166 more words)Show less

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.

Files

Just SKILL.md in .qwen/skills/bugfix of QwenLM/qwen-code.

Open the folder on GitHubat commit 4970bfa

Compare with similar skills

GitHub Issue Bugfix Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Issue Bugfix Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
GitHub Issue Bugfix Workflow this skillQwenLM/qwen-code	28k	—	~873	Automated safety check: Pass	Apache-2.0	today
Code Reviewyaklang/yakit	7.8k	—	~1.4k	Automated safety check: Notes	AGPL-3.0	7 days ago
Verdaccio Code Reviewverdaccio/verdaccio	18k	—	~853	Automated safety check: Pass	MIT	today
Octocode Code Researchbgauryy/octocode	946	—	~1.5k	Automated safety check: Pass	MIT	4 days ago
Code Reviewsortie-ai/sortie	196	—	~2.9k	Automated safety check: Pass	MIT	today
Panel Reviewstacklok/mecatl	218	—	~5.8k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Code Review
yaklang/yakit
对 Yakit 仓库的代码改动做规范化 code review：按代码逻辑、TS 定义、UI 引用与 Props、CSS 样式、依赖版本、配置项六个维度审查，检查测试用例缺失，强制执行 tsc 类型检查与 vitest 测试验证，输出「结果汇总 / 明细解释 / 合并结论」三块报告，经用户确认后写入文件。当用户要求 review、审查、评审代码改动，或在提交、合并、提 PR…
7.8k GitHub stars~1.4k tokensUpdated 7 days ago
DevelopmentAuto-check: notes
Verdaccio Code Review
verdaccio/verdaccio
Reviews a verdaccio diff, branch or PR against the repository's review guide, verifies each finding in the code and reports only actionable issues.
18k GitHub stars~853 tokensUpdated today
DevelopmentAuto-check passed
Octocode Code Research
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
946 GitHub stars~1.5k tokensUpdated 4 days ago
DevelopmentAuto-check passed
Code Review
sortie-ai/sortie
Reviews pull requests in this repository for the defect classes a mechanical checklist misses: documentation that outlived the code it describes, reaction and retry state that leaks or clobbers a…
196 GitHub stars~2.9k tokensUpdated today
DevelopmentAuto-check passed
Panel Review
stacklok/mecatl
Review completed non-trivial code across four independent axes: Spec, Standards, Test adequacy, and installed Domain specialists.
218 GitHub stars~5.8k tokensUpdated today
DevelopmentAuto-check passed
Jules
sanjay3290/ai-skills
Delegate coding tasks to Google Jules AI agent for asynchronous execution.
430 GitHub starsUsed in 1 repo~2.1k tokens
DevelopmentAuto-check passed

Questions about GitHub Issue Bugfix Workflow

What does GitHub Issue Bugfix Workflow do?

Fixes a bug from a GitHub issue by reproducing it first with a test-engineer subagent, then fixing, verifying, adding regression tests and reviewing the diff. The skill takes a GitHub issue URL or number and insists on reproduction before any fix, since fixing without a reproduction tends to give incomplete fixes and regressions.qwen/issues/ using the gh CLI, then spawns a test-engineer agent whose only goal is to reproduce the bug and write a report.

When should I use GitHub Issue Bugfix Workflow?

GitHub Issue Bugfix Workflow fits situations like: fixing a bug reported in a GitHub issue in the Qwen Code repository; investigating a user-reported problem where the failure must be reproduced first; adding regression coverage and a review pass after a bug fix.

How do I install GitHub Issue Bugfix Workflow in Claude Code?

Run `npx skills add QwenLM/qwen-code --skill bugfix -a claude-code`. Or copy the skill folder (.qwen/skills/bugfix in QwenLM/qwen-code) into .claude/skills/bugfix in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Bugfix Workflow in Codex?

Run `npx skills add QwenLM/qwen-code --skill bugfix -a codex`. Or copy the skill folder (.qwen/skills/bugfix in QwenLM/qwen-code) into .agents/skills/bugfix in your project. Codex loads it when a task matches its description.

Can I use GitHub Issue Bugfix Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add QwenLM/qwen-code --skill bugfix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bugfix, .gemini/skills/bugfix, .github/skills/bugfix and .opencode/skills/bugfix in your project.

What does GitHub Issue Bugfix Workflow need to run?

Going by SKILL.md and its folder, GitHub Issue Bugfix Workflow needs the command-line tools its instructions call (npm, gh and node). Our summary lists: The gh CLI, authenticated for the repository; Node.js and npm for the build and bundle steps; A test-engineer subagent.

Does GitHub Issue Bugfix Workflow access the network?

SKILL.md contains no URLs. Its commands use npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Issue Bugfix Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Issue Bugfix Workflow use?

GitHub Issue Bugfix Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issue Bugfix Workflow use?

About 873 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Issue Bugfix Workflow?

Skills that share tags, products or a category with GitHub Issue Bugfix Workflow: Code Review (yaklang/yakit, 7.8k stars), Verdaccio Code Review (verdaccio/verdaccio, 18k stars), Octocode Code Research (bgauryy/octocode, 946 stars) and Code Review (sortie-ai/sortie, 196 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Bugfix Workflow?

QwenLM (a GitHub organization) maintains it in QwenLM/qwen-code, which has 28,337 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 7, 2026.

Source: QwenLM/qwen-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install GitHub Issue Bugfix Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bugfix Workflow

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

Files

Compare with similar skills

Similar skills

More from QwenLM/qwen-code

Related

Questions about GitHub Issue Bugfix Workflow