BUG REPRODUCTION / Astral Software Inc.
uv reproduce-bug
Decides whether a reported uv behavior can be reproduced, and refuses to treat source inspection as a reproduction.
“Determine whether the behavior described in `.issue-triage-event.json` can be reproduced.”
01 / THE REASONING
Why this made the selection.
- The outcome is one of reproducible, not_reproducible, or needs_more_information. A reproduced behavior is not treated as proof the behavior is wrong.
- not_reproducible requires a targeted attempt. If a test already covers the behavior, the reason has to name the repository-relative path and the test name after the assertions were read. A simplified fixture that passes is not enough.
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/reproduce-bug.md
- agents/codex/config.toml
- LICENSE-MIT
- agents/schemas/issue-triage-bug.json
- .github/workflows/reproduce-bug.yml (launch configuration, selected context preparation and downstream job permissions)
- Round 2: pinned definition, output contract and permission/dependency boundaries reread 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 prompt says not to execute scripts copied from the issue and to use the uv binary already on PATH.
- The output schema permits exactly reproduction and reason, with no extra properties and three named reproduction outcomes.
- The launch step explicitly supplies the reproduce-bug permission profile, the schema, a temporary uv cache and the prompt file; the reviewed workflow limits its uv runner setup to Linux x64 and macOS ARM64.
- The report job obtains contents:write separately from the reproduction job, confirming that downstream persistence must be reviewed as its own action.
- A successful simplified fixture is explicitly insufficient to label the reported case not_reproducible.
- The prompt separates observing a behavior from deciding it is incorrect, and requires release/history inspection when the report alleges a regression.
Not established by this review
- The agent was not executed; model behaviour, host compatibility and task outcomes were not runtime-tested.
- No uv command, Codex invocation or GitHub workflow was run.
- Later reporting/retry job permissions were inspected; their full implementation and credential broker were not security-audited.
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.
- Read the prompt at the reviewed commit. No install command is published.
- 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.
- uv reproduce-bug ↗Checked
https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/reproduce-bug.md
Supports: summary, whySelected, limitations
- Codex permission profiles ↗Checked
https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/codex/config.toml
Supports: permission profile
- MIT licence ↗Checked
https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT
Supports: Redistribution terms, Copyright (c) 2025 Astral Software Inc.
- Structured output schema ↗Checked
https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/schemas/issue-triage-bug.json
Supports: Required output keys, Allowed decisions and extra-property rejection
https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/.github/workflows/reproduce-bug.yml
Supports: Prompt/schema/profile wiring, Separate downstream mutation privileges