
Pr Status Triage
If you're working on the Next.js monorepo, this automates the tedious work of checking PR status across CI jobs and review threads. It runs a background script, parses the results, and walks you through failures in priority order: build and lint first, then tests. What's smart here is it knows about flaky tests and won't make you chase ghosts. It'll help you reproduce failures locally with the right environment variables, reply to review comments, and even retrigger failed jobs when you're just waiting on known flakes. The workflow loops up to five times, which feels about right for dealing with CI in a massive repo. Saves you from manually clicking through dozens of GitHub tabs.
- skills.sh installs
- 839
- GitHub stars
- 139.5K
- last updated
- May 16, 2026
Install
$ npx -y skills add vercel/next.js --skill pr-status-triage --agent claude-codeInstalls into .claude/skills of the current project.
Files
PR Status Triage
Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.
Workflow
Start by fetching data to answer the user's query:
- For a targeted question about specific review comments, run
node scripts/pr-status.js [PR] --comments-only. This skips all Actions run, job, log, and flaky-test requests. - For CI status or general triage, run
node scripts/pr-status.js [PR](no--wait) to snapshot the current state, then start triaging immediately from the jobs that have already finished. Re-fetch on demand as more results land instead of waiting for the whole workflow to complete. - Use
--waitonly when the final run state itself is what you need: confirming an all-green run before handing back, or picking up results after retriggering failed jobs.
Then:
Sponsors
Details
- Repository
- github.com/vercel/next.js
- Categories
- Frontend Development, Git & Pull Requests, Cloud & Infrastructure
- First seen
- Apr 16, 2026