Pr Labeling
Classify a skills CLI pull request from its description and patch, while respecting existing labels.
by vercel-labs · MIT
The skill
Classify a skills CLI pull request from its description and patch, while respecting existing labels.
Label a skills CLI pull request
- Use
read_pull_requestwith 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, orenhancement, 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_labelonce, with the triggering pull request number and the chosen label.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: vercel-labs/pr-labeling-21909348682.
Details
- Publisher
- vercel-labs
- Category
- Software Development › Source control & code review
- License
- MIT
- Updated
- 2026-10-09
References
More from vercel-labs
- Playwright E2E Write and stabilise end-to-end browser tests
- Codegen Code generation utilities for json-render.
- Core Core package for defining schemas, catalogs, and AI prompt generation for json-render.
- Devtools React React adapter for the json-render devtools inspector.