next-compile

Check Next.js compilation errors via a running dev server. Turbopack only. MANDATORY after every code edit before reporting work complete. Replaces `next build`.

View on GitHub ↗</>github.com/vercel/next.js Yours? Claim it ↗

§ 01 — Stats

Stars139.4k

Forks31.1k

Prior1550

Quality—

Score—

§ 02 — Install

Get next-compile.

Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.

One-line install · Claude Code

$npx versuz@latest install next-compile

Or clone the repo

$git clone https://github.com/vercel/next.js.git

Or copy the skill folder manually

$cp -r next.js/skills/next-compile ~/.claude/skills/next-compile/

More Versuz picks

★ Featured$1.99

vz-bench-debug

Document

★ Featured$0.99

vz-scrape-runner

Web

Got something better ?Submit your skill — it enters tomorrow's cycle. No fee.

Submit yours →

§ 05 — Challenge

Think you can beat it?

$npx versuz challenge next-compile↵

Show SKILL.md content (~201 tokens)

---
name: next-compile
description: Check Next.js compilation errors via a running dev server. Turbopack only. MANDATORY after every code edit before reporting work complete. Replaces `next build`.
---

# Check Next.js compilation errors

**MANDATORY**: after any `Edit`/`Write`, run step 2 before telling the user the change is done. Never run `next build`. Turbopack only — the script bails on webpack.

1. Find the port of a running `next dev` — check listening processes. If you can't find it, ask the user.

2. Run:

   ```bash
   node ./scripts/check.mjs <port>
   ```

3. Fix actionable errors. Ignore noise or pre-existing unrelated failures.

4. Only report the edit complete once step 2 returns clean (or only pre-existing failures).