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/index.md.
Analyze each job-{id}.md and thread-{N}.md file 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.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 # 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
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: vercel-next-js-pr-status-triage3description: PR Status Triage4---56# PR Status Triage78Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.910## Workflow11121. Run `node scripts/pr-status.js --wait` in the background (timeout 1 min), then read `scripts/pr-status/index.md`.132. Analyze each `job-{id}.md` and `thread-{N}.md` file for failures and review feedback.143. Prioritize blocking jobs first: build, lint, types, then test jobs.154. Treat failures as real until disproven; check the "Known Flaky Tests" section before calling anything flaky.165. Reproduce locally with the same mode and env vars as CI.176. After addressing review comments, reply to the thread describing what was done, then resolve it. See `thread-N.md` files for ready-to-use commands.187. 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.1920## Quick Commands2122```bash23node scripts/pr-status.js # current branch PR24node scripts/pr-status.js <number> # specific PR25node scripts/pr-status.js [PR] --wait # background mode, waits for CI to finish26node scripts/pr-status.js --skip-flaky-check # skip flaky test detection27```2829## References3031- [workflow.md](./workflow.md) — prioritization, common failure patterns, resolving review threads32- [local-repro.md](./local-repro.md) — mode/env matching and isolation guidance3334---35> Converted and distributed by [TomeVault](https://tomevault.io/claim/vercel) — claim your Tome and manage your conversions.36<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/vercel-next-js-pr-status-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
PR Status Triage It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.