Next.js Documentation Updater

Problem Context

In the Next.js repository, code changes often ripple into API references, configuration pages, and guides. Maintainers reviewing PRs need to determine which docs are affected, whether a page is Pages Router shared content, and where new feature documentation should live. This skill turns that “diff-to-documentation” path into a repeatable workflow.

How It Works

• It starts with git diff canary...HEAD --stat to inspect changed files, then maps them to docs using references/CODE-TO-DOCS-MAPPING.md and directories such as docs/01-app/03-api-reference/.
• For existing docs, it reads the current structure, frontmatter, and router-specific content, then identifies new props, behavior changes, deprecations, and missing examples. Each proposed edit is confirmed before being applied.
• For new features, it selects the right doc type—component, function, config, guide, or file convention—uses kebab-case naming, applies the API Reference or Guide template, and adds related frontmatter links.
• It validates frontmatter, code block filenames, TypeScript/JavaScript switchers, props tables, and related links, and runs pnpm lint.

Scope and Caveats

This skill is aimed at Next.js documentation maintenance, especially App Router pages and shared Pages Router content. It relies on repository references such as references/DOC-CONVENTIONS.md and the code-to-docs mapping; if those files are incomplete, the output will depend on existing doc structure. It asks for confirmation before edits but still requires human judgment for API semantics and migration guidance.