gh-issues
Create and manage GitHub issues with duplicate detection and hierarchy support. Use when creating issues, filing bugs, tracking tasks, managing sub-issues, or organizing parent/child relationships. Triggers on "create issue", "file bug", "track this", "sub-issue", "parent issue", "break down", "list sub-issues".
📖 中文导读:Create and manage GitHub issues with duplicate detection and hierarchy support. Use when creating issues, filing bugs, tracking tasks, managing sub-issues, or organizing parent/child relationships. Triggers on "create issue", "file bug", "track this", "sub-issue", "parent issue", "break down", "list sub-issues". 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: gh-issues description: Create and manage GitHub issues with duplicate detection and hierarchy support. Use when creating issues, filing bugs, tracking tasks, managing sub-issues, or organizing parent/child relationships. Triggers on "create issue", "file bug", "track this", "sub-issue", "parent issue", "break down", "list sub-issues".
GitHub Issues Management
Routing
Creating a new issue? → Read references/creating.md
- Duplicate detection, codebase analysis, solution research
- Out-of-scope issue tracking during development
Managing issue hierarchy? → Read references/hierarchy.md
- Create/list/remove sub-issues
- Check parent issues
- Decide: new parent vs add to existing
Both? (Creating an issue as a sub-issue):
- Follow creating.md workflow to draft and create the issue
- Then follow hierarchy.md to link it as a sub-issue
Quick Commands
# Get current repo
gh repo view --json owner,name --jq '"\(.owner.login)/\(.name)"'
# Create issue
gh issue create --title "type(area): description" --body "content"
# View issue
gh issue view <number>
# List issues
gh issue list --state open --limit 20
Title Conventions
Use conventional format:
fix(area): description- Bug fixesfeat(area): description- New featuresrefactor(area): description- Code improvementsdocs(area): description- Documentationchore(area): description- Maintenance
Issue Body Template
## Summary
[1-2 sentences]
## Context
[Background, how discovered, why it matters]
## Current Behavior (for bugs)
[What happens now]
## Expected Behavior
[What should happen]
## Additional Context
[Related issues, links, etc.]