---
title: "uv workflow-failure: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/astral-uv-workflow-failure/
description: "Classifies one failed uv workflow as flaky or deterministic, and as create, duplicate, or ignore."
---

# uv workflow-failure: review, role & definition · Undominated.ai

> Classifies one failed uv workflow as flaky or deterministic, and as create, duplicate, or ignore.

[← Explore all agents](/agents/)

CI DIAGNOSIS / Astral Software Inc.

# uv workflow-failure

Classifies one failed uv workflow as flaky or deterministic, and as create, duplicate, or ignore.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/diagnose-workflow-failure.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 6 linked sources
 Publisher Astral Software Inc.
 Licence [MIT ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT)
 Revision c0110fc79aea
 [Read what was—and wasn’t—checked ↓](#review)

“Diagnose the failed workflow described in `.workflow-failure-event.json` and `.workflow-failure-log.txt` for the repository in this checkout.”

 [Astral Software Inc. · upstream description ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/diagnose-workflow-failure.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - flaky is allowed only when every independent root cause is transient. One deterministic failure makes the run deterministic. Dependent cancellations are not independent root causes.
- A red pull request is not by itself a reason to open an issue. ignore is an explicit outcome. The body has to carry the run URL and the error excerpt, and the prompt forbids @mentions.

### A good fit for

 - Supply the failed-run event JSON and selected job logs to classify independent failures and rule out duplicate tracking issues.
- Obtain a structured handoff containing related items/search scope, decision, failure kind, rationale, optional comment note and issue draft.
- Supply the workflow event and logs for every failed matrix job.
- Classify the run after separating independent root causes from cancellations and repeated downstream failures.

### Weigh up before choosing

 - The prompt assumes astral-sh/uv and uv-dev issue searches and repository labels. Another project must adapt those names, the input collector and reporting destinations.
- Read-only diagnosis does not describe the entire workflow: a separate retry job obtains actions:write and a separate report job obtains issues:write.
- A schema-valid flaky result is still a model judgment. Mixed or uncertain failures must remain deterministic under the prompt’s rules.
- The configured network profile allows GitHub; no live issue search, retry or publication was tested.
- The prompt produces a diagnosis/draft, while subsequent workflow jobs can retry or publish; those write permissions are a separate boundary.

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/diagnose-workflow-failure.md
- agents/prompts/triage-issue.md
- agents/codex/config.toml
- LICENSE-MIT
- agents/schemas/workflow-failure.json
- .github/workflows/diagnose-workflow-failure.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.
- decision is create, duplicate, or ignore. failure_kind is flaky or deterministic.
- The schema requires related, decision, failure_kind, decision_reason, comment_note and issue; the issue object remains required for duplicate/ignore outcomes even though its text is empty.
- The workflow supplies the workflow-failure profile and exact schema to the diagnosis call. Later retry and report jobs independently request write credentials.
- Issue drafts contain one constrained label and a decisive error excerpt. The prompt requires search scope and ruled-out candidates so duplicate checking is reviewable.
- flaky applies only when every independent root-cause failure is transient; a mixed or uncertain run must not be dismissed wholesale.
- Duplicate issue notes are reserved for material differences in the occurrence, and drafts must avoid mentions and sensitive values.

### 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.

[Upstream setup instructions ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/diagnose-workflow-failure.md)
 - 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

### Compatibility

A Codex prompt file a workflow can pass to a reviewer

### Implementation

Markdown

### Prompt text. The named profile is read-only plus GitHub network. Later jobs that create issues are outside this file.

 - Read the checkout and the supplied log
- Use gh for the related-issue search the prompt incorporates
- No checkout write in this prompt

### Cost model

MIT prompt text at no charge. Copyright (c) 2025 Astral Software Inc. The Apache licence file at this commit was not the grant used.

04 / FOLLOW THE EVIDENCE

## The source trail.

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

 - [uv workflow-failure ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/diagnose-workflow-failure.md) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/diagnose-workflow-failure.md Supports: summary, whySelected, limitations
- [Codex permission profiles ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/codex/config.toml) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/codex/config.toml Supports: permission profile
- [MIT licence ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT Supports: Redistribution terms, Copyright (c) 2025 Astral Software Inc.
- [Structured output schema ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/schemas/workflow-failure.json) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/schemas/workflow-failure.json Supports: Required output keys, Allowed decisions and extra-property rejection
- [Workflow launch and downstream-job permissions ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/.github/workflows/diagnose-workflow-failure.yml) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/.github/workflows/diagnose-workflow-failure.yml Supports: Prompt/schema/profile wiring, Separate downstream mutation privileges
- [Related issue search guidance ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/triage-issue.md) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/triage-issue.md Supports: Search breadth, Candidate rationale

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### uv reproduce-bug ↗ Decides whether a reported uv behavior can be reproduced, and refuses to treat source inspection as a reproduction.](/agents/astral-uv-reproduce-bug/)[### Monorepo architect ↗ Chooses a monorepo tool from the repository's constraints instead of naming one by fashion.](/agents/wshobson-monorepo-architect/)[### uv changelog editorial ↗ Rewrites only the newest uv changelog section, and keeps the version, date, pull-request numbers, and URLs as they are.](/agents/astral-uv-changelog-editorial/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
