PR Labeling

Classify a skills CLI pull request from its description and patch, while respecting existing labels.

1 minute · 149 words · 1 sections

Install

$ npx skills add vercel-labs/skills --skill pr-labeling

$ npx skills add vercel-labs/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Label a skills CLI pull request

Use read_pull_request with the number in the trigger message. Read the title, description, current labels, and changed file patches. If the head commit no longer matches the triggered commit, stop so a newer run can classify it.
If the pull request already has bug, documentation, or enhancement, stop. Keep labels chosen by maintainers or earlier runs.
Choose one label from the primary change supported by the patch:
- documentation: changes only documentation, examples, or explanatory text, without changing CLI behavior.
- bug: corrects existing CLI behavior, including installation, update checks, source parsing, agent detection, or security checks.
- enhancement: adds or intentionally expands CLI behavior, commands, agent support, or integration support.
If the patch is truncated, mixed, or insufficient to classify confidently, stop without adding a label. Do not infer a label from the title alone.
Use add_label once, with the triggering pull request number and the chosen label.

About this skill

Also published for: Vc — collapsed into this chapter because the copies are the same skill.
Source: .automations/pr-labeling/skills/pr-labeling/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/vercel-labs/skills, branch main, last pushed 6 November 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

4 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 4 distinct layouts observed: .automations/pr-labeling/skills/*/SKILL.md, .automations/triage/skills/*/SKILL.md, .vc/automations/workflows/triage/skills/*/SKILL.md, skills/*/SKILL.md.

Duplicates collapsed

1 mirror copy folded into their canonical skill — republished for Vc. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from the awesome-design-md registry — hue 2°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “1 heading” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /vercel-labs/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Label a skills CLI pull request

Use read_pull_request with the number in the trigger message. Read the title, description, current labels, and changed file patches. If the head commit no longer matches the triggered commit, stop so a newer run can classify it.

If the pull request already has bug, documentation, or enhancement, stop. Keep labels chosen by maintainers or earlier runs.

Choose one label from the primary change supported by the patch:

documentation: changes only documentation, examples, or explanatory text, without changing CLI behavior.
bug: corrects existing CLI behavior, including installation, update checks, source parsing, agent detection, or security checks.
enhancement: adds or intentionally expands CLI behavior, commands, agent support, or integration support.

If the patch is truncated, mixed, or insufficient to classify confidently, stop without adding a label. Do not infer a label from the title alone.

Use add_label once, with the triggering pull request number and the chosen label.