pr-labeling · git:20261105.e80e825 · 2026-11-05 · sha256 1f794aeb1e511000
pr-labeling git:20261105.e80e825A
Immutable. This exact content never changes and is served at /api/v1/blob/1f794aeb1e511000.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zcvos3ghzf6jmp42/1f794aeb1e5110008980aff363197f8cf3e37c71eedc498d7c56dc8e7bfbc5a5.json
Then /plugin install pr-labeling@markdownregistry-zcvos3ghzf6jmp42 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
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
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.