create-issue · fcakyon — Claude Code skill: create GitHub issues
create-issue is a Claude Code skill for drafting or revising issues about bugs and missing features. It can also refine an issue title or body before publication.
Apache-2.0 ★ 1,216 updated 2026-10-24
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install github-dev@claude-settingsWhat create-issue does
The skill turns a problem into an issue with reproduction steps, observed behavior, and the outcome being requested. It follows the repository’s issue template when one exists; otherwise, it uses a compact structure. For a feature request, it describes the current workflow that exposes the gap. It does not invent reproduction steps for a problem that has not been reproduced.
Before publishing, the skill checks repository guidance, searches for an existing issue, and verifies claims. It creates or edits issues with gh issue create or gh issue edit, using --title and --body-file, then reads back the published text. Publishing or editing requires the GitHub CLI gh. When revising an issue, it keeps useful attachments, links, and user edits, and does not broaden the scope without direction.
What it helps with
- write a bug report with reproducible steps
- describe a missing feature through the current workflow
- revise an existing issue title and body
- remove repeated explanations and diagnostic clutter
Example prompts for the agent
- Create an issue for the bug where checkout returns to the wrong page.
- Rewrite this issue’s title and body to follow the repository template.
- Draft a feature issue based on the current workflow.
How to install create-issue
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install github-dev@claude-settingsThis installs the whole github-dev plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill create-issue -a claude-code3Manually: put the files in place
~/.claude/skills/create-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-issue/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill create-issue -a codex2Manually: put the files in place
.agents/skills/create-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill create-issue -a cursor2Manually: put the files in place
.cursor/skills/create-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/github-dev/skills/create-issue2Manually: put the files in place
.github/skills/create-issue/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill create-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/github-dev/skills/create-issueManually: put the files in place
.devin/skills/create-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-issue
How do I install create-issue in Claude Code?
Add the marketplace with /plugin marketplace add fcakyon/claude-codex-settings, then install the plugin with /plugin install github-dev@claude-settings.
What does create-issue do?
It drafts or revises issues about bugs and missing features. Before publishing, it checks repository guidance, looks for an existing issue, and verifies claims.
What is required to publish an issue with create-issue?
Creating or editing an issue uses the GitHub CLI gh.
Source text
SKILL.md · Apache-2.0
--- name: create-issue description: This skill should be used when the user asks to "create an issue", "file a bug", "report a problem", "rewrite an issue", or "improve an issue title or body". --- # Create or revise an issue An issue describes a problem or missing capability. A PR describes a proposed change. Keep their writing rules separate. For PRs, use [create-pr](../create-pr/SKILL.md). ## Title Use a concise statement of the problem, naming the affected behavior. Do not use an imperative change request such as "Fix", "Add", "Enable", or "Keep" as the default. - "Visitor country is unavailable to upstream apps" - "GeoIP data becomes stale on running installations" - "Login returns to the wrong page after checkout" ## Body Follow the repository's issue template and the user's requested format. Otherwise use: ```markdown ## Problem One or two sentences naming the failure and its effect. ## Reproduction 1. The relevant setup or version. 2. The smallest steps that demonstrate the problem. ## Current behavior What was observed, with a short error or result when useful. ## Desired behavior The outcome the reporter needs. ``` For a missing feature, reproduce the current workflow that exposes the gap. If the problem was not reproduced, say so instead of inventing steps or results. Add environment details, evidence, or a proposed approach only when they help a maintainer act. Keep a possible implementation separate from the desired outcome. Remove repeated explanations, promotional claims, conversation history, full diagnostic dumps, and details that do not help reproduce or resolve the issue. A few useful sections are better than a long narrative or a checklist of every investigation step. ## Publish or update Inspect repository guidance and templates, search for an existing issue, and verify the claims before publishing. When revising, read the current issue and preserve useful attachments, links, and user edits. Do not expand an issue's scope without user direction. Use `gh issue create` or `gh issue edit` with `--title` and `--body-file`. Read back the published title and body. Link related PRs, but use a closing reference only when the PR addresses the issue's complete desired outcome.
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings
Similar skills
All skills for Git and GitHub →create-issue by other authors comes first.