Productivity
pr-status-triage▌
vercel/next.js · updated Apr 8, 2026
$npx skills add https://github.com/vercel/next.js --skill pr-status-triage
summary
Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.
skill.md
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 --waitin the background (timeout 1 min), then readscripts/pr-status/index.md. - Analyze each
job-{id}.mdandthread-{N}.mdfile 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. See
thread-N.mdfiles 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 # current branch PR
node scripts/pr-status.js <number> # specific PR
node scripts/pr-status.js [PR] --wait # background mode, waits for CI to finish
node scripts/pr-status.js --skip-flaky-check # skip flaky test detection
References
- workflow.md — prioritization, common failure patterns, resolving review threads
- local-repro.md — mode/env matching and isolation guidance