Official agent skill

PR Status Triage

by vercel in vercel/next.js

Triage CI failures and PR review comments using scripts/pr-status.js.

OfficialMITAuto-check passedTesting & QA

Install PR Status Triage

skills CLI
$ npx skills add vercel/next.js --skill pr-status-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vercel/next.js pr-status-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-status-triage .claude/skills/pr-status-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-status-triage
GitHub stars
143k
Token cost
~866 tokens
SKILL.md length
307 words
Files
3
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Triage CI failures and PR review comments using scripts/pr-status.js.

  • Works in 7 steps: Read scripts/pr-status/results/index.md. → For a targeted review question, inspect… → Prioritize blocking jobs first: build,… → …
  • Investigating failing CI jobs
  • SKILL.md covers Workflow, CI Analysis Tips, Quick Commands and References
  • Calls node, pnpm and cargo

What it does

PR Status Triage is an agent skill from vercel/next.js, published by the product's own GitHub organization. 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.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `local-repro.md` and `workflow.md`).

It sits in Testing & QA, covering Failing and flaky tests, Pull requests and Prioritization frameworks. It works with Turborepo and Next.js. The licence is MIT.

When your agent uses it

  • Investigating failing CI jobs
  • PR review feedback

Example prompts

  • “/pr-status-triage”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read scripts/pr-status/results/index.md.
  2. For a targeted review question, inspect the relevant thread-{N}.md, review-{id}.md, or comment-{id}.md files. For full triage, also…
  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 test failures locally with the same mode and environment as CI (e.g. dev or start, webpack or turbopack).
  6. After addressing review comments, reply to the thread describing what was done, then resolve it. Use reply-and-resolve-thread to do both…
  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…

What it can do on your machine

Read from SKILL.md and the folder at commit d8bfc3c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node
    • pnpm
    • cargo
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Status Triage loads about 866 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 307 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~866

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vercel/next.js at commit d8bfc3c, republished under its MIT licence (© vercel). 307 words, ~866 tokens.

Download SKILL.mdSave it as .claude/skills/pr-status-triage/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
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

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] --wait in the background (timeout 1 min).

Then:

  1. Read scripts/pr-status/results/index.md.
  2. For a targeted review question, inspect the relevant thread-{N}.md, review-{id}.md, or comment-{id}.md files. For full triage, also analyze each job-{id}.md and review file for failures and 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 test failures locally with the same mode and environment as CI (e.g. dev or start, webpack or turbopack).
  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.

CI Analysis Tips

  • Prioritize CI failures over review comments.
  • Prioritize blocking jobs first: build, lint, types, then test jobs.
  • Common fast checks:
    • rust check / build → Run cargo fmt -- --check, then cargo fmt
    • lint / build → Run pnpm prettier --write <file> for prettier errors
    • test failures → Run the specific failing test path locally

Run tests in the mode (e.g.):

bash
# Development mode with Turbopack
pnpm test-dev-turbo test/path/to/test.ts

# Production build and start with Webpack
pnpm test-start-webpack test/path/to/test.ts

Quick Commands

bash
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 [PR] --comments-only  # reviews/comments only; skips CI jobs
node scripts/pr-status.js --skip-flaky-check  # skip flaky test detection

Thread interaction:

bash
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

© vercel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .agents/skills/pr-status-triage of vercel/next.js.

  • SKILL.md
  • local-repro.md
  • workflow.md

Open the folder on GitHubat commit d8bfc3c

Compare with similar skills

PR Status Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Status Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Status Triage this skillvercel/next.js143k—~866Automated safety check: PassMIT
Debug Os Failure On GitHubstrands-agents/box299—~1.3kAutomated safety check: NotesApache-2.0
Fix Flakeskubernetes-sigs/agent-sandbox4.2k—~1.1kAutomated safety check: PassApache-2.0
Testingtrieb-work/nextjs-turbo-redis-cache151—~1.1kAutomated safety check: PassMIT
Babysit PRZenUml/web-sequence150—~871Automated safety check: PassMIT
Pre Commitwellwelwel/poku1.2k—~728Automated safety check: PassMIT

Similar skills

  • Debug Os Failure On GitHub

    strands-agents/box

    Debug a CI failure on an OS you are not on (you are on Linux, it fails on macos-latest, or the reverse) without opening a pull request per attempt.

    299 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check: notes
  • Fix Flakes

    kubernetes-sigs/agent-sandbox

    Official

    Diagnose and fix flaky tests tracked as open kind/flake issues in kubernetes-sigs/agent-sandbox — reproduce the flake, apply a minimal fix, and open a PR linking the issue.

    4.2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Testing

    trieb-work/nextjs-turbo-redis-cache

    Run tests and add Next.js version coverage for the cache handler.

    151 GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Babysit PR

    ZenUml/web-sequence

    Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.

    150 GitHub stars~871 tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Pre Commit

    wellwelwel/poku

    Run the mandatory pre-commit checks for the poku repository before staging a commit.

    1.2k GitHub stars~728 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Testing Validation

    AbdelStark/worldforge

    A skill your agent uses when selecting, running, or fixing WorldForge validation: pytest, coverage, ruff, generated provider docs, MkDocs strict build, package contract, CI failures, and release…

    108 GitHub stars~871 tokensUpdated 21 days ago
    Testing & QAAuto-check passed

More from vercel/next.js

All 27 skills in this repo
  • Gh Stack

    vercel/next.js

    Official

    Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack.

    143k GitHub starsUsed in 8 repos~2.3k tokens
    Auto-check passed
  • Sandbox Bench

    vercel/next.js

    Official

    Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…

    143k GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Next Dev Loop

    vercel/next.js

    Official

    Verify Next.js runtime behavior after editing app code. An agent skill from vercel/next.js.

    143k GitHub starsUsed in 9 repos~2.3k tokens
    Auto-check passed
  • Docs Diagrams

    vercel/next.js

    Official

    Draw diagrams for the Next.js docs in the style of the ones already published there: the light/dark PNGs an mdx references with <Image srcLight="/docs/light/<name.png" srcDark="/docs/dark/<name.png".

    143k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Official

    Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces.

    143k GitHub starsUsed in 6 repos~8.3k tokens
    Auto-check passed
  • React Sync

    vercel/next.js

    Official

    Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.

    143k GitHub stars~486 tokensUpdated today
    Auto-check passed

Categories

Questions about PR Status Triage

What does PR Status Triage do?

Triage CI failures and PR review comments using scripts/pr-status.js. js, published by the product's own GitHub organization.js.

When should I use PR Status Triage?

PR Status Triage fits situations like: investigating failing CI jobs; PR review feedback.

How do I install PR Status Triage in Claude Code?

Run `npx skills add vercel/next.js --skill pr-status-triage -a claude-code`. Or copy the skill folder (.agents/skills/pr-status-triage in vercel/next.js) into .claude/skills/pr-status-triage in your project. Claude Code loads it when a task matches its description.

How do I install PR Status Triage in Codex?

Run `npx skills add vercel/next.js --skill pr-status-triage -a codex`. Or copy the skill folder (.agents/skills/pr-status-triage in vercel/next.js) into .agents/skills/pr-status-triage in your project. Codex loads it when a task matches its description.

Can I use PR Status Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel/next.js --skill pr-status-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-status-triage, .gemini/skills/pr-status-triage, .github/skills/pr-status-triage and .opencode/skills/pr-status-triage in your project.

What does PR Status Triage need to run?

Going by SKILL.md and its folder, PR Status Triage needs the command-line tools its instructions call (node, pnpm, cargo and gh).

Does PR Status Triage access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is PR Status Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Status Triage use?

PR Status Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Status Triage use?

About 866 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Status Triage?

Skills that share tags, products or a category with PR Status Triage: Debug Os Failure On GitHub (strands-agents/box, 299 stars), Fix Flakes (kubernetes-sigs/agent-sandbox, 4.2k stars), Testing (trieb-work/nextjs-turbo-redis-cache, 151 stars) and Babysit PR (ZenUml/web-sequence, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Status Triage?

vercel (a GitHub organization, an official publisher) maintains it in vercel/next.js, which has 143,100 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 10, 2026.

Source: vercel/next.js on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.