# Diagnose A Red Run

Test is red, typecheck failed, CI job failed, flaky, timed out, was this already broken.

- Repository: https://github.com/different-ai/openwork (24362 stars)
- Category: Testing
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add different-ai/openwork --skill diagnose-a-red-run -g -a claude-code -y`
Codex: `npx skills add different-ai/openwork --skill diagnose-a-red-run -g -a codex -y`
Cursor: `npx skills add different-ai/openwork --skill diagnose-a-red-run -g -a cursor -y`
Gemini CLI: `npx skills add different-ai/openwork --skill diagnose-a-red-run -g -a gemini-cli -y`

## Description

Test is red, typecheck failed, CI job failed, flaky, timed out, was this already broken. Use to classify any failing check before changing code or calling it pre-existing.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill: Diagnose a Red Run

## Capture the branch failure

- Record the exact command, commit SHA, exit code, and passed/failed/skipped
  counts. Quote the first actionable failure; do not summarize it away.
- Classify the check: testkit spec, typecheck, build, lint, or CI job.

## Run a clean control

Never call a failure pre-existing from memory or from a modified checkout.

```bash
git fetch origin dev
git worktree add /tmp/openwork-dev-control --detach origin/dev
# In that clean worktree, prepare the same prerequisites and run the exact command.
git worktree remove /tmp/openwork-dev-control
```

- Keep tool versions, environment, services, flags, and secrets equivalent.
- Quote the control command, `origin/dev` SHA, exit code, counts, and matching
  failure text.
- Classify as pre-existing only when the clean control demonstrates the same
  failure. Otherwise classify it as introduced, environment-specific, or
  unresolved. A non-reproducing control is not proof of flakiness; repeat both
  sides before using that label.

## Classify by signature

- Unit/type/CI-only failure: inspect the first failing job and run its exact
  command locally before broadening scope.
- Vision disagreement on identical pixels: claim wording or product ambiguity.
  Make the product unambiguous or make the claim factual.
- Timeout with an On-screen dump: read it. It names the state; for example,
  `/session` can expose a steer-back race.
- Auth `403 INVALID_ORIGIN`: inspect Den trusted origins.
- Authorize URL points at the real provider: Den booted without mock env.
- Teardown `403 fresh_auth_required`: the session aged; a `freshSession` retry
  exists.

## Red core journey (`pr-proof.yml` "Core journey")

The rest: https://github.com/different-ai/openwork/blob/HEAD/.opencode/skills/diagnose-a-red-run/SKILL.md