
Update Docs
If you're a Next.js maintainer reviewing PRs, this walks you through keeping docs in sync with code changes. It analyzes git diffs to figure out which documentation files need updates, then guides you step by step through the changes with confirmation prompts before each edit. The useful part is the code-to-docs mapping and the scaffolding templates for new features, plus it handles the AppOnly and PagesOnly component conventions for router-specific content. Includes lint validation to catch formatting issues before you commit. Built for the workflow where you're already looking at a branch and need to methodically work through the documentation debt.
- skills.sh installs
- 2.4K
- GitHub stars
- 139.5K
- last updated
- May 16, 2026
Install
$ npx -y skills add vercel/next.js --skill update-docs --agent claude-codeInstalls into .claude/skills of the current project.
Files
Next.js Documentation Updater
Guides you through updating Next.js documentation based on code changes on the active branch. Designed for maintainers reviewing PRs for documentation completeness.
Quick Start
- Analyze changes: Run
git diff canary...HEAD --statto 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 lintto check formatting - Commit: Stage documentation changes
Workflow: Analyze Code Changes
Step 1: Get the diff
# See all changed files on this branch
git diff canary...HEAD --stat
# See changes in specific areas
git diff canary...HEAD -- packages/next/src/
Step 2: Identify documentation-relevant changes
Look for changes in these areas:
Sponsors
Details
- Repository
- github.com/vercel/next.js
- Categories
- Frontend Development, Documentation, Automation & Workflows, Cloud & Infrastructure