Menu
Apply consistent labels to GitHub issues. Use when creating or categorizing issues by type and priority.
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
Run the project's verification commands before claiming work complete. Use ALWAYS when finishing a task, claiming work done, committing, or creating a PR. Blocks completion until all checks pass.
Create atomic GitHub issues with clear acceptance criteria. Use when breaking down work into single-iteration tasks that can be picked up and completed independently.
Create well-structured GitHub milestones. Use when planning new phases of work that group related issues together.
Background knowledge about npm native binary corruption in Docker sandboxes
Laravel invokable controller patterns with Inertia. Use when creating endpoints, adding pages, building CRUD, or when user asks to "create an endpoint", "add a controller", "build a page", "add a store action", "create show page".
Inertia.js page component patterns with TypeScript. Use when creating pages or when user asks to "create a page", "build a component".
| name | github-labels |
| description | Apply consistent labels to GitHub issues. Use when creating or categorizing issues by type and priority. |
You use a standard set of labels to categorize and prioritize issues.
| Label | Color | Description |
|---|---|---|
type:bug | Red (#d73a4a) | Something isn't working |
type:feature | Blue (#0075ca) | New feature or enhancement |
type:refactor | Gray (#666666) | Code improvement, no behavior change |
type:docs | Purple (#7057ff) | Documentation only |
| Label | Color | Description |
|---|---|---|
priority:high | Red (#b60205) | Should be done first |
priority:medium | Yellow (#fbca04) | Normal priority |
priority:low | Green (#0e8a16) | Nice to have |
When selecting the next issue to work on:
high > medium > low > unlabeledPreferred: gh CLI
Apply labels when creating issues:
gh issue create \
--title "Issue title" \
--body "Issue body" \
--label "priority:high" \
--label "type:feature"
Add labels to existing issues:
gh issue edit <issue-number> --add-label "priority:high" --add-label "type:bug"
Fallback: GitHub MCP
If gh CLI is unavailable:
Tool: mcp__github__create_issue
Parameters:
owner: "<repo-owner>"
repo: "<repo-name>"
title: "Issue title"
body: "<issue body>"
labels: ["priority:high", "type:feature"]
milestone: <milestone-number>
Common combinations:
| Scenario | Labels |
|---|---|
| Critical bug | type:bug, priority:high |
| New feature | type:feature, priority:medium |
| Tech debt | type:refactor, priority:low |
| README update | type:docs, priority:low |