Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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**.
…
The line at the top of this page pins the label git:20260611.4f1203b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_oupann44y2kay5hk
GET https://markdownregistry.com/api/v1/resolve?ref=qwenlm/qwen-code/create-issue
GET https://markdownregistry.com/api/v1/blob/5e2975e11519428db0c8c38c561bfaba980e2254995d833742e4241cd0637c14
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
qwenlm/qwen-code · .qwen/skills/agent-reproduce-align/SKILL.md · Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen…
qwenlm/qwen-code · .qwen/skills/agent-reproduce-feature/SKILL.md · Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference…
qwenlm/qwen-code · .qwen/skills/autofix/SKILL.md · Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from…
qwenlm/qwen-code · .qwen/skills/deflake/SKILL.md · Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.
qwenlm/qwen-code · .qwen/skills/e2e-testing/SKILL.md · Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic…
qwenlm/qwen-code · .qwen/skills/find-simplifications/SKILL.md · Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned…
fcakyon/claude-codex-settings · plugins/github-dev/skills/create-issue/SKILL.md · This skill should be used when the user asks to "create an issue", "file a bug", "report a problem", "rewrite an…
tobihagemann/turbo · claude/skills/create-issue/SKILL.md · Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue"…
tobihagemann/turbo · codex/skills/create-issue/SKILL.md · Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue"…
mulhamna/jira-commands · plugin/skills/create-issue/SKILL.md · Create new Jira issues with jirac, including interactive prompts for project, issue type, summary, and custom fields
tomzx/agents · skills/create-issue/SKILL.md · Create a GitHub issue with background, prioritized acceptance criteria (Must/Should), and a justified time budget.
nateslabach/skills · skills/create-issue/SKILL.md · Craft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired…
phmatray/tagout · plugins/tagout/skills/create-issue/SKILL.md · Create a fully-seeded GitHub issue — not a bare `issue-create` call: template-compliant, carrying a brainstorm → spec →…
