菜单
Create and manage GitHub issues following project conventions. Use when creating issues, managing issue labels, assigning issues, setting up milestones, or asking about issue conventions and requirements.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write feature specification documents (SPEC.md). Use when creating a new feature spec, documenting feature requirements, defining feature scope and boundaries, or when the user asks to write or create a spec for a feature.
Create and manage iteration plans. Use when starting a new iteration, writing an iteration plan, breaking down requirements into tasks, planning sprint work, or asking about iteration plan format and structure.
Create pull requests and manage the PR workflow. Use when creating a PR, reviewing PRs, managing feature branch merges, or asking about PR conventions, code review process, or the collaborative feature branch workflow.
Create iteration retrospective issues. Use when writing a retrospective, closing out an iteration, reflecting on iteration progress, or asking about retrospective format.
Best practices for writing and auditing Claude Code SKILL.md files. Use when creating a new skill, editing an existing skill, auditing skills, improving skill frontmatter, optimizing skill descriptions for auto-triggering, or asking about skill file structure, frontmatter fields, or allowed-tools configuration.
| name | github-issues |
| description | Create and manage GitHub issues following project conventions. Use when creating issues, managing issue labels, assigning issues, setting up milestones, or asking about issue conventions and requirements. |
| argument-hint | issue title or number |
| allowed-tools | ["Read","Grep","Glob","Bash(gh issue *)","Bash(gh api *)","Bash(gh label *)"] |
iteration-planning — creates issues from the task breakdownpr-workflow — PRs reference issues via Closes #<number>Every issue must have:
feature, task, or bugThe project uses these labels:
feature — new functionalitytask — development work that isn't a feature or bugbug — something that's brokenretrospective — added alongside task for retrospective issuesIf labels don't exist yet, create them:
gh label create feature --description "New functionality" --color 0E8A16
gh label create task --description "Development task" --color 1D76DB
gh label create bug --description "Something is broken" --color D93F0B
gh label create retrospective --description "Iteration retrospective" --color FBCA04
Milestones are named "Iteration 1" through "Iteration 4". Create them if they don't exist:
gh api repos/{owner}/{repo}/milestones -f title="Iteration 1"
If you contribute to an issue but aren't assigned, analytics won't attribute the work to you.
Read the matching template in .github/ISSUE_TEMPLATE/ (feature.yml, task.yml, or bug.yml) and use its structure for the --body. Example:
gh issue create \
--title "Add search-by-title to items list endpoint" \
--label "feature" \
--milestone "Iteration 1" \
--assignee "owner,supporting" \
--body "## Description
Add a query parameter to the items endpoint that filters by title.
## Acceptance Criteria
- [ ] Search is case-insensitive
- [ ] Empty query returns all items
- [ ] Tests added for all cases"
For task and bug issues, follow the same pattern using the corresponding template structure.