Labsco
vercel logo

pr-status-triage

✓ Official★ 140,300

by vercel · part of vercel/next.js

Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.

🔥🔥✓ VerifiedFreeQuick setup
#git
🔒 Repo-maintenance skill. It exists to help maintain vercel/next.js itself — it's only useful if you contribute code to that project.

Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

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

  1. Run node scripts/pr-status.js --wait in the background (timeout 1 min), then read scripts/pr-status/results/index.md.
  2. Analyze each job-{id}.md and thread-{N}.md file in scripts/pr-status/results/ for failures and review feedback.
  3. Prioritize blocking jobs first: build, lint, types, then test jobs.
  4. Treat failures as real until disproven; check the "Known Flaky Tests" section before calling anything flaky.
  5. Reproduce locally with the same mode and env vars as CI.
  6. 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.
  7. 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

Copy & paste — that's it
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

Thread interaction:

Copy & paste — that's it
node scripts/pr-status.js reply-thread <threadNodeId> "<body>"           # reply to a review thread
node scripts/pr-status.js resolve-thread <threadNodeId>                  # resolve a review thread
node scripts/pr-status.js reply-and-resolve-thread <threadNodeId> "<body>"  # reply and resolve in one step

References

  • workflow.md — prioritization, common failure patterns, resolving review threads
  • local-repro.md — mode/env matching and isolation guidance