メニュー
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create a loop that runs a prompt now and follows up either on a fixed schedule or through self-paced wakeups. Usage - /loop check the build, /loop 5m check the build, /loop check the PR every 30m. /loop list to show jobs, /loop clear to cancel all.
Answer any question about Qwen Code usage, features, configuration, and troubleshooting by referencing the official user documentation. Also helps users view or modify their settings.json. Invoke with `/qc-helper` followed by a question, e.g. `/qc-helper how do I configure MCP servers?` or `/qc-helper change approval mode to yolo`.
Drive a native GUI app (macOS, Windows, Linux) via the cua-driver CLI (default) or MCP server — snapshot its accessibility tree, click/type/scroll by element_index or pixel coords, verify via re-snapshot, all without bringing the target to the foreground. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real application on the host.
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an extension locally. Invoke with `/extension-creator` followed by an extension path and optional template name.
Create pixel-art desktop pet companions for Qwen Code. Generates a customized chibi spritesheet (1536×1872, 8×9 grid) for any character the user names — F1 drivers, anime characters, celebrities, fictional characters, animals, etc. Use when the user says "desktop pet", "桌宠", "桌面宠物", "想要XXX当桌宠", "换个宠物", or similar.
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
| 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> |
| allowedTools | ["run_shell_command","read_file","write_file","glob","grep_search"] |
Take the user's idea or bug description, investigate the codebase for context, draft an issue for review, and submit once approved.
The user provides a brief description of a feature request or bug report via the skill argument.
Determine whether the request is a feature request or a bug report.
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.
.github/ISSUE_TEMPLATE/feature_request.yml.github/ISSUE_TEMPLATE/bug_report.ymlUse the template's field labels and descriptions to structure the draft.
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:
<details>
<summary>中文</summary>
(Chinese translation here)
</details>
Present the draft. Iterate on feedback until the user is satisfied. Do not submit until the user explicitly approves.
When the user confirms, create the issue with gh issue create:
gh issue create --title "..." --body-file .qwen/issues/draft-<slug>.md
Apply labels based on type:
type/feature-request, status/needs-triagetype/bug, status/needs-triageReport the issue URL back to the user.