来源信息
- 仓库
- gitkraken/vscode-gitlens
- 最近来源活动
- 2026年9月3日 20:38
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 9,928
- 分支
- 1,801
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- create-issue
- description
- Create GitHub issues from uncommitted changes or commits
# /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
1. **Collect diff**: uncommitted (`git diff`), single commit (`git show <sha>`), or range (`git diff <range>`)
2. **Classify**: bugfix / feature / refactor / docs / tests
3. **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 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 |
```bash
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
1. Describe behavior, not implementation — issues are public and their readers are users, so no code snippets, diffs, or internal details
2. NEVER include credentials or secrets
3. NEVER create labels without user confirmation
4. **NEVER auto-create issues or edit CHANGELOG without user confirmation**
在 GitHub 查看