skills/ vercel-labs/skills

pr-labeling

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

0
Installs
—
Rating
—
Success rate
1
Files scanned
Scan passedmethodology
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

1 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 0c5521767a69a586… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

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.

Files

1
1.2 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from vercel-labs/skills2

Related methodology skillsscan passed