Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Labels a pull request in the skills CLI repo as bug, documentation or enhancement based on its description and patch, leaving existing labels untouched.
Install Skills CLI PR Labeling
$ npx skills add vercel-labs/skills --skill pr-labeling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/skills pr-labeling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.factory/workflows/pr-labeling/skills/pr-labeling .claude/skills/pr-labeling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-labeling" agent skill from https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labeling into .claude/skills/pr-labeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-labeling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labelingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel-labs/skills --skill pr-labeling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/skills pr-labeling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.factory/workflows/pr-labeling/skills/pr-labeling .agents/skills/pr-labeling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-labeling" agent skill from https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labeling into .agents/skills/pr-labeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-labeling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/skills --skill pr-labeling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/skills pr-labeling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.factory/workflows/pr-labeling/skills/pr-labeling .cursor/skills/pr-labeling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-labeling" agent skill from https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labeling into .cursor/skills/pr-labeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-labeling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel-labs/skills.git --path .factory/workflows/pr-labeling/skills/pr-labeling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel-labs/skills --skill pr-labeling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/skills pr-labeling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.factory/workflows/pr-labeling/skills/pr-labeling .gemini/skills/pr-labeling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-labeling" agent skill from https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labeling into .gemini/skills/pr-labeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-labeling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel-labs/skills pr-labelingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel-labs/skills --skill pr-labeling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.factory/workflows/pr-labeling/skills/pr-labeling .github/skills/pr-labeling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-labeling" agent skill from https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labeling into .github/skills/pr-labeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-labeling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/skills --skill pr-labeling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/skills pr-labeling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.factory/workflows/pr-labeling/skills/pr-labeling .opencode/skills/pr-labeling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-labeling" agent skill from https://github.com/vercel-labs/skills/tree/main/.factory/workflows/pr-labeling/skills/pr-labeling into .opencode/skills/pr-labeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-labeling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-labeling- GitHub stars
- 33k
- Token cost
- ~310 tokens
- SKILL.md length
- 157 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Labels a pull request in the skills CLI repo as bug, documentation or enhancement based on its description and patch, leaving existing labels untouched.
- Works in 5 steps: Use read_pull_request with the number in… → If the pull request already has bug,… → Choose one label from the primary change… → …
- A new pull request to the skills CLI repo needs a type label
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Automated triage where labels set by maintainers must be kept
What it does
The agent reads the pull request through a read_pull_request tool, looking at the title, description, current labels and changed file patches, and stops if the head commit no longer matches the one that triggered the run. If the PR already has bug, documentation or enhancement, it does nothing. Otherwise it picks one label from the main change: documentation for docs-only edits, bug for fixes to existing CLI behavior, and enhancement for new or expanded behavior. It then calls add_label once. If the patch is truncated, mixed or unclear, it adds no label and never guesses from the title alone.
When your agent uses it
- A new pull request to the skills CLI repo needs a type label
- Automated triage where labels set by maintainers must be kept
Example prompts
- “Classify the newest skills CLI pull request and add the right label.”
- “Check whether this PR only changes docs, and label it if it has no type label yet.”
Requirements
- Tools to read a pull request and add a label (read_pull_request and add_label)
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Use read_pull_request with the number in the trigger message. Read the title, description,
- If the pull request already has bug, documentation, or enhancement, stop. Keep labels
- Choose one label from the primary change supported by the patch
- If the patch is truncated, mixed, or insufficient to classify confidently, stop without adding
- Use add_label once, with the triggering pull request number and the chosen label.
What it can do on your machine
Read from SKILL.md and the folder at commit 87a2669. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skills CLI PR Labeling loads about 310 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 157 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vercel-labs/skills at commit 87a2669, republished under its MIT licence (© vercel-labs). 157 words, ~310 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-labeling/SKILL.md (or your agent's skills folder).- name
- pr-labeling
- description
- 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.
© vercel-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .factory/workflows/pr-labeling/skills/pr-labeling of vercel-labs/skills.
Open the folder on GitHubat commit 87a2669
Compare with similar skills
Skills CLI PR Labeling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skills CLI PR Labeling this skillvercel-labs/skills | 33k | — | ~310 | Automated safety check: Pass | MIT | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| Pre-Ship Review and Triagetw93/Waza | 7.2k | — | ~6.9k | Automated safety check: Pass | MIT | |
| Ouroboros Maintainer TriageQ00/ouroboros | 6.2k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
- Official
Review Triage Phase
prisma/orm
Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.
Pre-Ship Review and Triage
tw93/Waza
Reviews diffs and pull requests, triages issues, and checks release readiness, reporting findings with evidence and making no edits unless authorized.
Ouroboros Maintainer Triage
Q00/ouroboros
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
Issue and PR Triage
stickerdaniel/linkedin-mcp-server
Turns the open issues and pull requests of the linkedin-mcp-server repository into a read-only priority list for maintainers.
More from vercel-labs/skills
- Official
Triage
vercel-labs/skills
Identify focused, evidence-backed skills CLI bug fixes worth quuu's attention.
Related
Categories
Questions about Skills CLI PR Labeling
What does Skills CLI PR Labeling do?
Labels a pull request in the skills CLI repo as bug, documentation or enhancement based on its description and patch, leaving existing labels untouched. The agent reads the pull request through a read_pull_request tool, looking at the title, description, current labels and changed file patches, and stops if the head commit no longer matches the one that triggered the run. If the PR already has bug, documentation or enhancement, it does nothing.
When should I use Skills CLI PR Labeling?
Skills CLI PR Labeling fits situations like: A new pull request to the skills CLI repo needs a type label; automated triage where labels set by maintainers must be kept.
How do I install Skills CLI PR Labeling in Claude Code?
Run `npx skills add vercel-labs/skills --skill pr-labeling -a claude-code`. Or copy the skill folder (.factory/workflows/pr-labeling/skills/pr-labeling in vercel-labs/skills) into .claude/skills/pr-labeling in your project. Claude Code loads it when a task matches its description.
How do I install Skills CLI PR Labeling in Codex?
Run `npx skills add vercel-labs/skills --skill pr-labeling -a codex`. Or copy the skill folder (.factory/workflows/pr-labeling/skills/pr-labeling in vercel-labs/skills) into .agents/skills/pr-labeling in your project. Codex loads it when a task matches its description.
Can I use Skills CLI PR Labeling in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel-labs/skills --skill pr-labeling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-labeling, .gemini/skills/pr-labeling, .github/skills/pr-labeling and .opencode/skills/pr-labeling in your project.
What does Skills CLI PR Labeling need to run?
SKILL.md names no scripts, command-line tools or credentials: Skills CLI PR Labeling is instructions for the agent only. Our summary lists: Tools to read a pull request and add a label (read_pull_request and add_label).
Does Skills CLI PR Labeling access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skills CLI PR Labeling safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skills CLI PR Labeling use?
Skills CLI PR Labeling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skills CLI PR Labeling use?
About 310 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skills CLI PR Labeling?
Skills that share tags, products or a category with Skills CLI PR Labeling: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Review Triage Phase (prisma/orm, 48k stars) and Pre-Ship Review and Triage (tw93/Waza, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skills CLI PR Labeling?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/skills, which has 33,378 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: vercel-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.