label-issue

name	label-issue
description	Classify and label a GitHub issue based on repository-specific labeling instructions. Use when auto-labeling issues, classifying issue types (bug, feature, question), or adding priority/area labels. Triggers on "label issue", "classify issue", "what labels should this issue have".

Label Issue Skill

Automatically classify and apply labels to a GitHub issue using the available GitHub tools and repository-specific labeling rules.

Within labeling, explicit current-user instructions take precedence over validated labeling customization, which takes precedence over the built-in classification and output defaults below. Neither may change the labeling role, authorize an unrequested write, invent repository labels, remove existing labels, or override global security and repository-scope boundaries.

Workflow

1. Input: an issue reference (owner/repo + issue number, or an issue URL).
2. Fetch labeling instructions: follow the issuelens-config skill and call the issuelens-config tool for domain labeling. Use configured or legacy content when returned, subject to explicit user instructions. If the source is built-in, fall back to the repository's existing label set (list the repo labels) and use label names and descriptions to guide classification. If configuration loading fails, stop and do not apply labels.
3. Fetch the issue: read the issue title, body, existing labels, and comments with the GitHub tools.
4. Analyze the issue by default:
   • Type detection — bug, feature, question, etc. (match keywords against label names/descriptions).
   • Priority — identify severity indicators (core function broken, no workaround → high).
   • Area/component — match content against area-specific labels.
5. Apply labels: use the available add-labels operation to add the selected labels. Do not remove existing labels.
6. Report: list the labels applied and the reasoning for each.

Rules

• Only add labels that exist in the repository. Never invent labels.
• Preserve existing labels; only add.
• Prefer explicit user labeling requirements, then validated configured or legacy labeling instructions, then built-in classification.
• Use only the bundled IssueLens GitHub MCP tools for every GitHub read or write. Pass the explicit owner/repository to every tool. Never use shell commands, direct HTTP, or the GitHub CLI.

Output

By default, report the labeling decision:

• Labels applied: the labels added.
• Reasoning: why each label was chosen (type / priority / area).
• Existing labels: labels already present (left unchanged).