菜单
Creates required GitHub labels for issue tracking and workflow automation. Use when setting up a new repository, when labels are missing, or when the user asks to add or sync project labels.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | generate-git-labels |
| description | Creates required GitHub labels for issue tracking and workflow automation. Use when setting up a new repository, when labels are missing, or when the user asks to add or sync project labels. |
Ensures all required labels exist in the current GitHub repository for the pick-and-plan workflow.
| Label | Color | Description |
|---|---|---|
CONT | #7057ff | P0: Continue existing work |
CRITICAL | #d73a4a | P1: Critical issues |
BUG | #d73a4a | P2: Bug fixes |
MAINT | #0075ca | P3: Maintenance tasks |
DOC | #0075ca | P4: Documentation |
FEAT | #a2eeef | P5: New features |
| Label | Color | Description |
|---|---|---|
AIIGNORE | #eeeeee | AI should ignore this issue |
INPROGRESS | #fbca04 | Work in progress |
DELETEME | #eeeeee | Marked for deletion |
FUTUREWORK | #d4c5f9 | Deferred to future |
PLANCREATED | #c5def5 | Execution plan created |
Confirm you're in a git repository with a GitHub remote:
gh repo view --json name,owner
List current labels to avoid duplicates:
gh label list --json name
For each missing label, run:
gh label create "LABEL_NAME" --color "COLOR" --description "DESCRIPTION"
Priority Labels:
gh label create "CONT" --color "7057ff" --description "P0: Continue existing work"
gh label create "CRITICAL" --color "d73a4a" --description "P1: Critical issues"
gh label create "BUG" --color "d73a4a" --description "P2: Bug fixes"
gh label create "MAINT" --color "0075ca" --description "P3: Maintenance tasks"
gh label create "DOC" --color "0075ca" --description "P4: Documentation"
gh label create "FEAT" --color "a2eeef" --description "P5: New features"
Workflow Labels:
gh label create "AIIGNORE" --color "eeeeee" --description "AI should ignore this issue"
gh label create "INPROGRESS" --color "fbca04" --description "Work in progress"
gh label create "DELETEME" --color "eeeeee" --description "Marked for deletion"
gh label create "FUTUREWORK" --color "d4c5f9" --description "Deferred to future"
gh label create "PLANCREATED" --color "c5def5" --description "Execution plan created"
List all labels to confirm:
gh label list
Report:
Checking labels in owner/repo...
Existing labels: bug, enhancement, documentation
Missing labels: CONT, CRITICAL, BUG, MAINT, DOC, FEAT, AIIGNORE, INPROGRESS, DELETEME, FUTUREWORK, PLANCREATED
Creating labels...
✓ CONT (P0: Continue existing work)
✓ CRITICAL (P1: Critical issues)
✓ BUG (P2: Bug fixes)
✓ MAINT (P3: Maintenance tasks)
✓ DOC (P4: Documentation)
✓ FEAT (P5: New features)
✓ AIIGNORE (AI should ignore this issue)
✓ INPROGRESS (Work in progress)
✓ DELETEME (Marked for deletion)
✓ FUTUREWORK (Deferred to future)
✓ PLANCREATED (Execution plan created)
Done! 11 labels created.
Creates new projects and features following repository structure conventions. Use when the user wants to create a new project, add a new feature, scaffold code, or initialize a new module in this repository.
Executes a pending workplan by priority. Use when the user wants to execute a plan, work on a pending task, start implementation, or continue working on planned issues.
Picks an open GitHub issue by priority and creates an execution plan. Use when the user wants to work on issues, pick a task, plan work, or asks what to work on next.
Writes comprehensive unit tests using xUnit and Moq. Use when the user wants to create tests, add test coverage, write unit tests, or test new functionality. Always finds root cause of failures and fixes the code, not the tests.
Professional React/Node/TypeScript web developer with .NET backend expertise. Uses Context7 for current documentation, verifies all UI work in the browser, and maintains strict visual quality standards. Use when building web features, creating components, implementing APIs, or any frontend/fullstack development task.
Conducts professional code reviews of branch changes and documents findings. Use when the user wants a code review, asks to review changes, check code quality, or before creating a pull request.