Menu
Fetches GitHub labels, classifies them as defaults vs structured, and prompts the user for selection. Auto-consulted by /create-github-issue.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Add a dependency relationship between GitHub issues using the native addBlockedBy mutation
Reusable file sequence numbering with prefix (NNNN-name) and suffix (name-NNNN) modes. Returns the next available zero-padded sequence number for a given directory.
Drop a timestamped note for the current issue - collected by /finish-issue for PR descriptions
Create or update CHANGELOG entries with tone guardrails, thematic grouping, and implementation-detail leak detection.
Delete an issue's working directory (.claude-work/issues/<ID>/) after confirming with the user via interactive prompt
Create a commit message file in .claude-work/commit-msgs/ with auto-numbered filenames. Focuses on WHY not WHAT. The diff already shows what changed. User reviews and commits manually.
| name | label-discovery |
| version | 2026.07.27@6dc7d1d |
| user-invocable | false |
| description | Fetches GitHub labels, classifies them as defaults vs structured, and prompts the user for selection. Auto-consulted by /create-github-issue. |
| allowed-tools | Bash(gh label list *) |
Fetch labels from a GitHub repository, classify them, and prompt the user for selection.
Fetch all labels from the target repository. If the calling skill provides a --repo owner/repo override, pass it through:
gh label list --json name,description --limit 200
gh label list --repo owner/repo --json name,description --limit 200
Classify into two groups:
GitHub defaults: ship with every new repo, don't indicate structured usage:
Structured labels: anything beyond the defaults. Their presence indicates intentional label conventions (e.g., type:bug, priority:high, area:checkout).
Ask the user which labels to apply (simple multi-select from the defaults). The user can also choose "none".
Present them grouped by prefix (e.g., all type:* together, all priority:* together). Ask the user to select appropriate labels.
Example prompt:
This repo uses structured labels beyond GitHub defaults:
type: bug, enhancement, feature, refactor
priority: high, medium, low
area: checkout, admin, api
Other: good first issue, help wanted
Which labels should this issue have?
Use /question if the label choice requires extended discussion. Otherwise, use inline prompting.