agentsclimarketplace
Sign in

Pr status triage

Skill vercel/next.js/.agents/skills/pr-status-triage

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.From its SKILL.md

Install
npx -y skills add vercel/next.js --skill pr-status-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.3 KB, as published. Nobody here has run it

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

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:

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

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.