Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
Turns a feature idea or bug description into a drafted GitHub issue with a bilingual body and the right labels, then submits it with gh once you approve.
Install Create GitHub Issue
$ npx skills add QwenLM/qwen-code --skill create-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install QwenLM/qwen-code create-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.qwen/skills/create-issue .claude/skills/create-issue && rm -rf skills-srcUse ~/.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/
Install the "create-issue" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issue into .claude/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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 install https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issueType 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.
$ npx skills add QwenLM/qwen-code --skill create-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install QwenLM/qwen-code create-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.qwen/skills/create-issue .agents/skills/create-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-issue" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issue into .agents/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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.
$ npx skills add QwenLM/qwen-code --skill create-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install QwenLM/qwen-code create-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.qwen/skills/create-issue .cursor/skills/create-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-issue" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issue into .cursor/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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 https://github.com/QwenLM/qwen-code.git --path .qwen/skills/create-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add QwenLM/qwen-code --skill create-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install QwenLM/qwen-code create-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.qwen/skills/create-issue .gemini/skills/create-issue && rm -rf skills-srcUse ~/.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/
Install the "create-issue" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issue into .gemini/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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.
$ gh skill install QwenLM/qwen-code create-issueInstalls 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).
$ npx skills add QwenLM/qwen-code --skill create-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.qwen/skills/create-issue .github/skills/create-issue && rm -rf skills-srcUse ~/.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/
Install the "create-issue" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issue into .github/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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.
$ npx skills add QwenLM/qwen-code --skill create-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install QwenLM/qwen-code create-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.qwen/skills/create-issue .opencode/skills/create-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-issue" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/create-issue into .opencode/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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
create-issue- GitHub stars
- 28k
- Token cost
- ~534 tokens
- SKILL.md length
- 228 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Turns a feature idea or bug description into a drafted GitHub issue with a bilingual body and the right labels, then submits it with gh once you approve.
- Works in 6 steps: Classify → Investigate the codebase → Read the template → …
- Filing a feature request in a repository with issue templates
- SKILL.md covers Input and Steps
- Calls gh
What it does
The agent classifies the request as a feature request or bug report, investigates the codebase for relevant code and existing behavior, and checks related issues with gh issue list. It reads the matching issue template from .github/ISSUE_TEMPLATE and uses its field labels to structure a markdown draft saved under .qwen/issues for review. The draft is written from the user's perspective, avoids internal implementation details, keeps the title in English and puts an English body first with a Chinese translation in a collapsible block.
The draft is shown and revised until you are satisfied, and nothing is submitted without your explicit approval. Then gh issue create posts it with labels: type/feature-request or type/bug, plus status/needs-triage. The issue URL is reported back.
When your agent uses it
- Filing a feature request in a repository with issue templates
- Reporting a bug with codebase context included
- Writing issues with an English body and a Chinese translation
Example prompts
- “Create an issue for adding a dark mode toggle to the settings page.”
- “Draft a bug report: the export command hangs when the output folder does not exist.”
- “File a feature request for a --dry-run flag and show me the draft first.”
Requirements
- The GitHub CLI (`gh`) with access to the repository
- Issue templates under .github/ISSUE_TEMPLATE
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
Create GitHub Issue loads about 534 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 228 words of instructions outside code blocks.
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). 228 words, ~534 tokens.
Download SKILL.mdSave it as
.claude/skills/create-issue/SKILL.md (or your agent's skills folder).- name
- create-issue
- description
- Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
- argument-hint
- <feature idea or bug description>
Create Issue
Take the user's idea or bug description, investigate the codebase for context, draft an issue for review, and submit once approved.
Input
The user provides a brief description of a feature request or bug report via the skill argument.
Steps
1. Classify
Determine whether the request is a feature request or a bug report.
2. Investigate the codebase
Search for relevant code, files, and existing behavior related to the request.
Build a thorough understanding of how the current system works. Note any related
existing issues found via gh issue list --search.
3. Read the template
- Feature request → read
.github/ISSUE_TEMPLATE/feature_request.yml - Bug report → read
.github/ISSUE_TEMPLATE/bug_report.yml
Use the template's field labels and descriptions to structure the draft.
4. Draft the issue
Write a markdown draft to .qwen/issues/draft-<slug>.md for the user to review.
Rules:
Write from the user's perspective — not as an implementation spec.
Keep language clear and concise; avoid internal implementation details.
Title stays in English only.
Bilingual body: English content first, Chinese translation at the end wrapped in a collapsible block:
markdown <details> <summary>中文</summary> (Chinese translation here) </details>
5. Review with user
Present the draft. Iterate on feedback until the user is satisfied. Do not submit until the user explicitly approves.
6. Submit
When the user confirms, create the issue with gh issue create:
gh issue create --title "..." --body-file .qwen/issues/draft-<slug>.mdApply labels based on type:
- Feature request →
type/feature-request,status/needs-triage - Bug report →
type/bug,status/needs-triage
Report the issue URL back to the user.
© QwenLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .qwen/skills/create-issue of QwenLM/qwen-code.
Open the folder on GitHubat commit 4970bfa
Compare with similar skills
Create GitHub Issue 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Create GitHub Issue this skillQwenLM/qwen-code | 28k | — | ~534 | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK | 4.7k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Ouroboros Maintainer TriageQ00/ouroboros | 6.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| RTK Issue Triagertk-ai/rtk | 83k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| Verdaccio Issue Triageverdaccio/verdaccio | 18k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
Ouroboros Maintainer Triage
Q00/ouroboros
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
RTK Issue Triage
rtk-ai/rtk
Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.
Verdaccio Issue Triage
verdaccio/verdaccio
Triages an incoming verdaccio/verdaccio issue against the code, the affected release line and related issues, and picks labels from the repository's existing taxonomy.
Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
More from QwenLM/qwen-code
All 41 skills in this repoAgent Feature Reproduction
QwenLM/qwen-code
Reproduces a feature from Codex or Claude Code in Qwen Code by running the reference agent under capture, reading the traces, then implementing matching behavior.
Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Qwen Code Desktop Brand Builder
QwenLM/qwen-code
Builds a rebranded Qwen Code desktop package from the Tauri shell using only a brand id and a logo, with sensible derived defaults.
Qwen Code Memory Leak Debugger
QwenLM/qwen-code
Walks through capturing and comparing V8 heap snapshots to find memory leaks in the Qwen Code Node.js CLI, using tmux and the chrome-devtools CLI.
tmux Real User Testing
QwenLM/qwen-code
Drives Qwen Code in a real tmux session the way a user would and saves a readable step-by-step transcript of each screen for maintainers to review.
Related
Works with
Categories
Questions about Create GitHub Issue
What does Create GitHub Issue do?
Turns a feature idea or bug description into a drafted GitHub issue with a bilingual body and the right labels, then submits it with gh once you approve. The agent classifies the request as a feature request or bug report, investigates the codebase for relevant code and existing behavior, and checks related issues with gh issue list.qwen/issues for review.
When should I use Create GitHub Issue?
Create GitHub Issue fits situations like: filing a feature request in a repository with issue templates; reporting a bug with codebase context included; writing issues with an English body and a Chinese translation.
How do I install Create GitHub Issue in Claude Code?
Run `npx skills add QwenLM/qwen-code --skill create-issue -a claude-code`. Or copy the skill folder (.qwen/skills/create-issue in QwenLM/qwen-code) into .claude/skills/create-issue in your project. Claude Code loads it when a task matches its description.
How do I install Create GitHub Issue in Codex?
Run `npx skills add QwenLM/qwen-code --skill create-issue -a codex`. Or copy the skill folder (.qwen/skills/create-issue in QwenLM/qwen-code) into .agents/skills/create-issue in your project. Codex loads it when a task matches its description.
Can I use Create GitHub Issue 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 create-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-issue, .gemini/skills/create-issue, .github/skills/create-issue and .opencode/skills/create-issue in your project.
What does Create GitHub Issue need to run?
Going by SKILL.md and its folder, Create GitHub Issue needs the command-line tools its instructions call (gh). Our summary lists: The GitHub CLI (`gh`) with access to the repository; Issue templates under .github/ISSUE_TEMPLATE.
Does Create GitHub Issue access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Create GitHub Issue 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 Create GitHub Issue use?
Create GitHub Issue 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 Create GitHub Issue use?
About 534 tokens (SKILL.md is roughly 2.1k 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 Create GitHub Issue?
Skills that share tags, products or a category with Create GitHub Issue: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), WinAppSDK Triage Meeting Prep (microsoft/WindowsAppSDK, 4.7k stars), Ouroboros Maintainer Triage (Q00/ouroboros, 6.2k stars) and RTK Issue Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create GitHub Issue?
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.