next-compile
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.
-
Find the port of a running
next dev— check listening processes. If you can't find it, ask the user. -
Run:
node ./scripts/check.mjs <port> -
Fix actionable errors. Ignore noise or pre-existing unrelated failures.
-
Only report the edit complete once step 2 returns clean (or only pre-existing failures).
More from vercel/next.js
update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
2.3Kauthoring-skills
>
921runtime-debug
>
888react-vendoring
>
854flags
>
816dce-edge
>
759