Agent skill
create-issue
Create GitHub issues from uncommitted changes or commits
Install this agent skill to your Project
npx add-skill https://github.com/gitkraken/vscode-gitlens/tree/main/.claude/skills/create-issue
SKILL.md
/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 /changelog skill. Map: Feature→Added, Enhancement→Changed, Bugfix→Fixed, Removal→Removed.
Safety
- NEVER include code snippets, diffs, or implementation details in issues
- NEVER include credentials or secrets
- NEVER create labels without user confirmation
- NEVER auto-create issues or edit CHANGELOG without user confirmation
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
investigate
Structured investigation of a bug or unexpected behavior before implementing a fix
commit
Create well-formatted git commits following GitLens conventions
analyze
Deep design and implementation analysis with devil's advocate evaluation
add-command
Create new VS Code commands with all required boilerplate
add-icon
Add new icons to the GitLens GL Icons font
deep-planning
Use when formulating the best technical approach for a task — before writing implementation plans or code. Triggers on architecture decisions, complex features, refactors, or when the user asks how to approach something. Investigates current codebase, questions existing patterns, researches alternatives, and presents approaches with trade-offs.
Didn't find tool you were looking for?