How to use the Create GitHub Issue agent skill (create-issue)

What an agent skill is and what create-issue does

An agent skill is a folder containing a SKILL.md file that gives an AI coding agent a set of instructions and the tools it may use for a specific task. This skill's SKILL.md is the only file listed for it.

When you give the agent a feature idea or bug description, the skill tells it to classify the request as a feature request or a bug report, search the codebase and existing issues for context, and read the matching issue template from .github/ISSUE_TEMPLATE. The agent then writes a markdown draft to .qwen/issues/draft-<slug>.md for you to review.

• Classifies the request as a feature request or a bug report
• Searches the codebase and existing issues (via gh issue list --search) for related context
• Follows feature_request.yml or bug_report.yml field labels and descriptions
• Writes the draft to a file you can read and edit
• Submits only after you explicitly approve, then reports the issue URL

Install the create-issue skill

Download the ZIP for this skill from our page and unzip it. To make it available for your own use, place the unzipped skill folder in ~/.claude/skills/. To make it available only inside one project, place it in that project's .claude/skills/ folder.

If you use the Claude apps instead, you can upload the skill there under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills, then upload

Meet the requirements before you run it

The skill depends on several things in your environment. It runs shell commands through the agent, so you need to allow that, and it reads and writes files in your workspace. It submits issues with the GitHub CLI, so gh must be installed and authenticated with an account that can create issues. The repository must also contain .github/ISSUE_TEMPLATE files, because the skill reads feature_request.yml and bug_report.yml from there.

• GitHub CLI (gh) installed and authenticated with an account that can create issues
• A Git repository containing .github/ISSUE_TEMPLATE files
• Permission to run shell commands and read/write files in the workspace

Trigger the skill with a natural request

The skill takes a brief description as its argument, described in the source as '<feature idea or bug description>'. Describe the feature or the bug in plain language, and say that you want an issue drafted. The agent will then run the steps above.

Expect a review step. The skill presents the draft and iterates on your feedback. Nothing is posted until you explicitly approve it.

• Describe one feature or one bug per request
• Include what you saw or wanted, and where you saw it if you know
• Ask for changes to the draft before approving, if needed

Review the draft and approve submission

Open the draft file at .qwen/issues/draft-<slug>.md and read it before approving. The English body comes first, followed by a Chinese translation inside a collapsible block. The title stays in English only.

When you approve, the skill runs gh issue create with the title and the draft file as the body. It applies type/feature-request or type/bug, together with status/needs-triage, and reports the issue URL back to you.

• Check the title and the English body first
• Check that the Chinese translation matches the English content
• Approve only when the draft is what you want public

Safety notes: scripts and network access

This skill runs scripts and uses the network. Its submission step calls the GitHub CLI, which posts to GitHub, and the investigation step runs gh issue list --search. Posting publicly is hard to undo, which is why the skill waits for your explicit approval before it submits.

Read the draft file before you approve, and confirm that the gh account you are logged in with is the one you intend to post from.

• Submission creates a public issue on GitHub under your authenticated gh account
• The skill is designed to stop at the draft until you approve
• Review the draft for sensitive details before approval

Tips for better issues

The skill draws its structure from the repository's own templates, so the clearer your description, the more useful the draft. The skill also asks the agent to avoid internal implementation details, so describe what the user experiences rather than how the code should change.

• Give the user-visible symptom or the desired outcome
• Name the area of the product if you know it, so the codebase search is focused
• Use the review loop to fix wording before approving