04-issue-create — Claude Code skill: what it does, how to install
04-issue-create is a skill for Claude Code that prepares and opens issues in a configured project tracker. It asks for explicit approval before submitting a ticket.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-vcs@aidd-frameworkWhat 04-issue-create does
This skill detects your ticketing tool from project memory or infers it directly from the remote URL. It structures the issue body using assets/issue-template.md and checks assets/CONTRIBUTING.md for project-specific rules before drafting.
The issue-create action compiles reproduction steps, labels, and issue types into an actionable ticket. It never creates tickets silently: it halts to get approval on the title, body, labels, milestones, and project assignments. It is not designed for git commits, pull requests, or commenting on existing tickets.
What it helps with
- draft a bug report following repo guidelines
- detect the project issue tracker from repository settings
- verify title, labels, and milestone before opening a ticket
Example prompts for the agent
- Open an issue for the connection drop bug in the checkout form
- File a ticket to refactor the webhook handler
How to install 04-issue-create
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-vcs@aidd-frameworkThis installs the whole aidd-vcs plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 04-issue-create -a claude-code3Manually: put the files in place
~/.claude/skills/04-issue-create/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/04-issue-create/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 04-issue-create -a codex2Manually: put the files in place
.agents/skills/04-issue-create/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 04-issue-create -a cursor2Manually: put the files in place
.cursor/skills/04-issue-create/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-vcs/skills/04-issue-create2Manually: put the files in place
.github/skills/04-issue-create/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 04-issue-create -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-vcs/skills/04-issue-createManually: put the files in place
.devin/skills/04-issue-create/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 04-issue-create -a opencodeClaude.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 04-issue-create
How to install 04-issue-create in Claude Code?
Add the marketplace and install the package using /plugin marketplace add ai-driven-dev/framework followed by /plugin install aidd-vcs@aidd-framework. Alternatively, run npx skills add ai-driven-dev/framework --skill 04-issue-create -a claude-code.
What does 04-issue-create do?
It gathers context about a reported problem, formats it according to repository templates, and submits a new issue to your configured ticketing tool.
Can 04-issue-create open pull requests or leave comments?
No. The skill only files new issues; it does not commit changes, open pull requests, or post comments on existing threads.
Source text
SKILL.md · MIT
--- name: 04-issue-create description: Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue. argument-hint: problem --- # Issue Create Files well-formed issues in the configured tracker after gathering enough context to be actionable. ## Actions | # | Action | Role | Input | | --- | --------------- | -------------------------------------------------------------------------- | -------------------------------------- | | 01 | `issue-create` | Detect tool, fill template, validate, open the issue | problem_description, labels, type | Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - Detect the ticketing tool from project memory first, then fall back to inferring it from the remote URL. - Tool-agnostic: invoke whichever ticketing tool is configured for the project. - Always wait for explicit user approval of title, body, labels, type, projects, and milestones before creating. - Issue body follows `assets/issue-template.md`. - Be thorough and concise. Short sentences. Focus on clarity, reproduction steps, and expected behavior. - Read `assets/CONTRIBUTING.md` for project-specific issue rules before drafting. ## Assets - `assets/issue-template.md`: Issue / ticket body template. - `assets/CONTRIBUTING.md`: Contribution guidelines, including issue process.
© AI-Driven Dev · MIT · ai-driven-dev/framework