update-docs

Guides you through updating Next.js documentation based on code changes on the active branch. Designed for maintainers reviewing PRs for documentation completeness. Look for changes in these areas: Use the code-to-docs mapping in references/CODE-TO-DOCS-MAPPING.md to find corresponding documentation files. Example mappings: Before making changes, read the existing doc to understand: Common updates include: For each change: If the doc uses the source field pattern (common for Pages Router docs), the source file is the one to edit. Example: Edit the App Router source, not the Pages Router file. Use this when adding documentation for entirely new features. API Reference Template: Guide Template: Update frontmatter with related documentation: See references/DOC-CONVENTIONS.md for complete formatting rules. Frontmatter (required): Code blocks: Router-specific content: Notes: Before committing documentation changes: - Analyze changes : Run git diff canary...HEAD --stat to see what files changed - Identify affected docs : Map changed source files to documentation paths - Review each doc : Walk through updates with user confirmation - Validate : Run pnpm lint to check formatting - Commit : Stage documentation changes - src/client/components/image.tsx → docs/01-app/03-api-reference/02-components/image.mdx - src/server/config-shared.ts → docs/01-app/03-api-reference/05-config/ - Current...