← Explore all agents

PULL-REQUEST LABELS / Astral Software Inc.

uv pull-request labels

Chooses at most the semantic labels for one uv pull request, and leaves the list empty when the diff does not support one.

“Determine which labels should be added to the pull request described in `.pull-request-labels-event.json` for the repository in this checkout.”

01 / THE REASONING

Why this made the selection.

  • Labels have to come from .pull-request-labels.json. An unclear case is an empty array. The prompt says not to recommend labels already on the pull request and not to suggest removals.
  • Test-only changes stay internal:testing even when the tests reproduce a bug. CI-control, merge-control, deployment, codex, and bot labels are excluded. The classification follows the diff, not the issue text it mentions.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • agents/prompts/pull-request-labels.md
  • agents/codex/config.toml
  • LICENSE-MIT
  • Definition reread at the preserved revision; scoped workflow and output-contract review on 2026-10-14

Our findings

  • LICENSE-MIT is the MIT License. The copyright line is Copyright (c) 2025 Astral Software Inc. The prompts have no per-file copyright header.
  • The schema is named in the prompt and was not opened. The prompt itself says the labels array can be empty.
  • It classifies the actual change, so test-only reproducers are internal testing rather than product bug labels.
  • It uses recent label history for ambiguous meanings, excludes existing labels and control/automation-trigger labels, and allows an empty recommendation.

Not established by this review

  • The prompt was not run.
  • No GitHub issue, label, or pull request was created.
  • .pull-request-labels.json was not opened.
  • The pull-request-labels workflow was not opened.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the prompt at the reviewed commit. No install command is published.
  2. Do not treat the prompt as permission to post, commit, or push. The prompt text and the permission profile are separate from later workflow jobs.

Before you start

  • A checkout of astral-sh/uv at a revision the prompt can read

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. uv pull-request labels ↗Checked

    https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/pull-request-labels.md

    Supports: summary, whySelected, limitations

  2. https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/codex/config.toml

    Supports: permission profile

  3. MIT licence ↗Checked

    https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT

    Supports: Redistribution terms, Copyright (c) 2025 Astral Software Inc.

Evidence & Ask