How do I install the Create Issue skill?

Run npx skillmds@latest add gitkraken/create-issue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Create Issue skill do?

Create GitHub issues from uncommitted changes or commits It is listed under Coding & Dev Tools on SkillMD.

Is Create Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Issue?

gitkraken (@gitkraken) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Issue by gitkraken — Agent Skill

Name: Create Issue
Author: gitkraken

File contents

/create-issue - Create GitHub Issue

Analyze changes and create GitHub issues with CHANGELOG entries.

Usage

/create-issue [source]

source: "uncommitted", a commit SHA, or a range like "abc123..def456"

Workflow

Collect diff: uncommitted (git diff), single commit (git show <sha>), or range (git diff <range>)
Classify: bugfix / feature / refactor / docs / tests
Check duplicates: gh search issues --repo gitkraken/vscode-gitlens "<keywords>"
Create issue: generate title + body, confirm with user first
Update CHANGELOG: add entry to [Unreleased], confirm with user first

Duplicate Detection

Score matches 0-1:

Title similarity (>75% token overlap): +0.5
Body keyword overlap: +0.3
Same component: +0.15

Thresholds: >= 0.7 likely duplicate, 0.45-0.69 possibly related, < 0.45 ignore.

Issue Title

Describe the problem/need from user's perspective, not the solution
Be specific with context ("when switching repositories", "in large repos")
Concise, no trailing punctuation

Issue Body

Section	Content
Summary	One-line description
Impact	Who/what benefits
Validation	Steps to verify
Risk	Potential regressions

gh issue create --title "<title>" --body "<body>" --assignee @me --label "<labels>"

Labels

Fetch existing: gh label list --limit 100
ONLY use existing labels
Confirm with user before applying

CHANGELOG Entry

Format per /audit-commits CHANGELOG conventions. Map: Feature→Added, Enhancement→Changed, Bugfix→Fixed, Removal→Removed.

Safety

Describe behavior, not implementation — issues are public and their readers are users, so no code snippets, diffs, or internal details
NEVER include credentials or secrets
NEVER create labels without user confirmation
NEVER auto-create issues or edit CHANGELOG without user confirmation

---name: create-issuedescription: Create GitHub issues from uncommitted changes or commits---# /create-issue - Create GitHub IssueAnalyze changes and create GitHub issues with CHANGELOG entries.## Usage```/create-issue [source]```- `source`: "uncommitted", a commit SHA, or a range like "abc123..def456"## Workflow1. **Collect diff**: uncommitted (`git diff`), single commit (`git show <sha>`), or range (`git diff <range>`)2. **Classify**: bugfix / feature / refactor / docs / tests3. **Check duplicates**: `gh search issues --repo gitkraken/vscode-gitlens "<keywords>"`4. **Create issue**: generate title + body, **confirm with user first**5. **Update CHANGELOG**: add entry to `[Unreleased]`, **confirm with user first**## Duplicate DetectionScore matches 0-1:- Title similarity (>75% token overlap): +0.5- Body keyword overlap: +0.3- Same component: +0.15Thresholds: >= 0.7 likely duplicate, 0.45-0.69 possibly related, < 0.45 ignore.## Issue Title- Describe the _problem/need_ from user's perspective, not the solution- Be specific with context ("when switching repositories", "in large repos")- Concise, no trailing punctuation## Issue Body| Section | Content || ---------- | --------------------- || Summary | One-line description || Impact | Who/what benefits || Validation | Steps to verify || Risk | Potential regressions |```bashgh issue create --title "<title>" --body "<body>" --assignee @me --label "<labels>"```## Labels- Fetch existing: `gh label list --limit 100`- ONLY use existing labels- Confirm with user before applying## CHANGELOG EntryFormat per `/audit-commits` CHANGELOG conventions. Map: Feature→Added, Enhancement→Changed, Bugfix→Fixed, Removal→Removed.## Safety1. Describe behavior, not implementation — issues are public and their readers are users, so no code snippets, diffs, or internal details2. NEVER include credentials or secrets3. NEVER create labels without user confirmation4. **NEVER auto-create issues or edit CHANGELOG without user confirmation**

Frequently asked questions

Create Issue