AugmentClaude
DevOps

PR Labeler

By vercel-labs· vercel-labs/skills· 0

Automatically classify pull requests with labels based on their description and code changes.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/pr-labeling-vercel-labs/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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

What this skill does

Label a skills CLI pull request

  1. 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.
  2. If the pull request already has bug, documentation, or enhancement, stop. Keep labels chosen by maintainers or earlier runs.
  3. 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.
  4. 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.
  5. Use add_label once, with the triggering pull request number and the chosen label.

Related skills

N

n8n Architect

EtienneLescot

Create, edit, and validate n8n workflows and automation configurations.

D

Deploy to Vercel

vercel-labs

Deploy your app to Vercel with preview or production environments.

V

Vercel CLI with Tokens

vercel-labs

Deploy and manage Vercel projects using token-based authentication instead of interactive login.

S

Skill Installer

foryourhealth111-pixel

Install Codex skills from curated lists or GitHub repositories.