
update-docs
#10 in Documentation for DevelopersThis 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",…
Overview
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.From the project's GitHub description
Our editorial assessment of update-docs is still in review. Facts below come from the repository and our catalogue.
Good for
Technical specifications
Each attribute is labelled with where it came from.
Install
A skill is a set of instructions your agent loads. Install it into the agent you use; there is nothing to host.
$ npx skills add https://github.com/vercel/next.js --skill update-docs- Listing
- skills.shInstall counts come from skills.sh.
Alternatives
Also in Documentation for Developers
Same category, not necessarily equivalent.
microsoft-docs
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more.
writing-guidelines
Review docs/prose for Writing Guidelines compliance.
Reviews
Community ratings are kept separate from Beav Scout rankings.
No reviews yet. Community reviews and comments are opening soon; you'll be able to rate update-docs once signed in.