update-docs

To keep Next.js documentation in sync with code changes during a PR review, this Skill diffs the active branch against the canary branch, maps changed source files to documentation references, and proposes structured updates to ensure completeness before merging.

Mapping code paths to documentation references requires a mapping reference file. This Skill uses that reference alongside code diffs to identify affected Next.js docs and automatically scaffold or update documentation for new features across packages.

Yes, a mapping reference from code paths to docs is required. The documentation update workflow relies on this reference to connect source file changes on the active branch to the corresponding Next.js documentation files for accurate updates.

Documentation completeness validation works by linting and checking the updated docs against the code changes. It ensures consistent coverage across Next.js packages by verifying that all modified source files have corresponding updated documentation before merging.

Yes, you can scaffold new docs directly from an active branch diff. By analyzing the code changes against the canary branch, the Skill identifies unmapped new features and scaffolds the corresponding Next.js documentation structure automatically.