update-docs

Analyze code PR diffs and generate Next.js documentation updates.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/JuanDiego30/cermont_aplicativo --skill update-docs-juandiego30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/JuanDiego30/cermont_aplicativo/tree/main/.agents/skills/update-docs
Command: npx skills add https://github.com/JuanDiego30/cermont_aplicativo --skill update-docs-juandiego30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift between code and docs is common during PRs; this skill helps align Next.js docs with recent code changes to speed up reviews and reduce confusion.

Core Features & Use Cases

  • Guided diffs analysis to identify impacted docs across app/api-reference, guides, and metadata.
  • Suggest targeted edits and scaffold new sections when docs are missing, ensuring consistency with code.
  • Provide review-ready changes with formatting validation and conformance to project conventions.
  • Real-world use case: when a PR adds a new API feature, this skill maps touched code to the relevant docs and proposes precise edits.

Quick Start

Review the latest PR diff and generate a draft of required documentation updates.

Frequently Asked Questions about update-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep Next.js documentation in sync with code changes in a PR?

Documentation drift happens when code PRs modify features without updating corresponding docs, causing inconsistency; mapping diffs to docs paths identifies impacted sections for targeted edits.

How do I map changed code files to Next.js docs paths for updates?

This skill maps changed files to Next.js docs paths and scaffolds missing sections when documentation does not exist, ensuring consistency with recent code changes.

Can I generate review-ready documentation edits directly from a PR diff?

It enforces workflow steps including diff analysis, docs mapping, and formatting validation to produce structured, ready-to-apply documentation changes for Next.js projects.

Does this docs sync approach work for Next.js app, api-reference, and guides directories?

It applies to Next.js documentation updates across app/api-reference, guides, and metadata, mapping changed files to docs paths and generating review-ready edits.

What are the limitations of automated documentation mapping for code PRs?

Limitations include dependency on clear diff analysis and project conventions; it scaffolds new sections but requires review to ensure complete consistency with code changes.