create-issue
Create a GitHub issue with detailed description, purpose, and appropriate labels
Best use case
create-issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a GitHub issue with detailed description, purpose, and appropriate labels
Teams using create-issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-issue Compares
| Feature / Agent | create-issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a GitHub issue with detailed description, purpose, and appropriate labels
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create GitHub Issue ## Step 1: Gather Information Receive the issue topic from $ARGUMENTS or the user's description. If the information is insufficient, ask the user to clarify the following: - What needs to be done (the task or problem) - Why it needs to be done (the purpose or motivation) ## Step 2: Research Context Before writing the issue, investigate the relevant parts of the codebase to understand: - Which files and modules are affected - Existing related code patterns - Potential impact and scope of the change ## Step 3: Draft the Issue **Important: All issue content (title, body, labels) must be written in English**, regardless of the language used in the conversation with the user. Create a well-structured issue with the following sections: ```markdown ## Summary A concise one-liner describing what this issue is about. ## Motivation / Purpose Why this change is needed. Explain the problem, user impact, or improvement opportunity. ## Details Detailed description of what needs to be done: - Specific changes required - Files or modules likely affected - Acceptance criteria or expected behavior ## Additional Context Any relevant links, screenshots, or references (if applicable). ``` ## Step 4: Assign Labels First, get the available labels from the repository: ```bash gh label list ``` Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-defined, minimal domain knowledge required), also assign the `good first issue` label if it exists in the repository. ## Step 5: Create the Issue ```bash gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..." ``` ## Step 6: Report Result Output the created issue URL and a summary of: - Issue title - Assigned labels - Whether `good first issue` was applied and why (or why not)
Related Skills
create-scrap-issue
Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
security-scan-diff
Scan for malicious code in git diff between a tag/commit and HEAD
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
git-worktree-runner
Manages git worktrees using git-worktree-runner (gtr). Use when the user needs to create, list, remove, or navigate worktrees with `git gtr` commands, open editors or AI tools in worktrees, manage parallel development branches, or check out GitHub PRs (including from forks) into worktrees.
draft-release
Draft a new release of the project.
review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "/review-pr".
review-and-comments
Review a PR for code quality and security issues, then post review comments on it. Runs review-pr followed by post-review-comments sequentially.
rebase-latest-main
Fetch latest origin/main and rebase it onto the current branch, resolving conflicts if necessary. Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.
post-review-comments
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style