| name | pr-status-triage |
| description | Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.
|
| metadata | {"internal":true} |
PR Status Triage
Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.
Workflow
- Run
node scripts/pr-status.js --wait in the background (timeout 1 min), then read scripts/pr-status/results/index.md.
- Analyze each
job-{id}.md and thread-{N}.md file in scripts/pr-status/results/ for failures and review feedback.
- Prioritize blocking jobs first: build, lint, types, then test jobs.
- Treat failures as real until disproven; check the "Known Flaky Tests" section before calling anything flaky.
- Reproduce locally with the same mode and env vars as CI.
- After addressing review comments, reply to the thread describing what was done, then resolve it. Use
reply-and-resolve-thread to do both in one step, or use reply-thread + resolve-thread separately. See scripts/pr-status/results/thread-N.md files for ready-to-use commands.
- When the only remaining failures are known flaky tests and no code changes are needed, retrigger the failing CI jobs with
gh run rerun <run-id> --failed. Then wait 5 minutes and go back to step 1. Repeat this loop up to 5 times.
Quick Commands
node scripts/pr-status.js
node scripts/pr-status.js <number>
node scripts/pr-status.js [PR] --wait
node scripts/pr-status.js --skip-flaky-check
Thread interaction:
node scripts/pr-status.js reply-thread <threadNodeId> "<body>"
node scripts/pr-status.js resolve-thread <threadNodeId>
node scripts/pr-status.js reply-and-resolve-thread <threadNodeId> "<body>"
References
- workflow.md — prioritization, common failure patterns, resolving review threads
- local-repro.md — mode/env matching and isolation guidance
