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.

Install
npx skills add 'https://github.com/vercel/next.js/tree/canary/.agents/skills/pr-status-triage'
Download bundle ↓
canary · bfcf687Scanned 2026-09-15

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

local-repro.md

local-repro.mdBrowse 3 files
View on GitHub
← Back to SKILL.md

Local Reproduction Guide

Match CI Job Mode

  • Dev-mode failures: use pnpm test-dev-turbo or pnpm test-dev-webpack based on job mode.
  • Start-mode failures: use pnpm test-start-turbo or pnpm test-start-webpack.

Match CI Environment Variables

Read the "Job Environment Variables" section in index.md and mirror them locally. Key variables:

  • IS_WEBPACK_TEST=1 — forces webpack mode (turbopack is default locally).
  • NEXT_SKIP_ISOLATE=1 — skips package isolation; never use when verifying module resolution or build-time compilation fixes.
  • Feature flags like __NEXT_USE_NODE_STREAMS=true, __NEXT_CACHE_COMPONENTS=true change DefinePlugin replacements.

Example: a failure in "test node streams prod" needs:

IS_WEBPACK_TEST=1 __NEXT_USE_NODE_STREAMS=true __NEXT_CACHE_COMPONENTS=true NEXT_TEST_MODE=start

Isolation Rule

When validating module-resolution, entrypoint-export, or internal require-path fixes, rerun without NEXT_SKIP_ISOLATE=1.

One-Run Log Analysis

Capture once, analyze multiple times:

HEADLESS=true pnpm test-dev-turbo test/path/to/test.ts > /tmp/test-output.log 2>&1
grep "●" /tmp/test-output.log
grep -A5 "Error:" /tmp/test-output.log
tail -5 /tmp/test-output.log
Referenced from SKILL.md