update-docs

Map code diffs to Next.js MDX docs and guide content updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides maintainers to synchronize documentation with code changes, ensuring docs accurately reflect current features, APIs, and usage during PR reviews.

Core Features & Use Cases

  • Code-to-doc mapping: identifies affected docs from code changes and maps them to the correct MDX pages.
  • Frontmatter-driven updates: ensures pages include proper title, description, and related links following project conventions.
  • PR workflow automation: provides a repeatable process for auditing, scaffolding new docs for new features, and validating docs with linting rules.

Quick Start

Review the active branch changes and map them to the corresponding docs using the provided mappings, then update the documentation with validated frontmatter and content.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I update Next.js documentation to reflect code changes during a PR review?

To update Next.js documentation during a PR review, you map code diffs to the appropriate MDX pages using code-to-docs mappings, then guide content edits while enforcing frontmatter validation and lint checks.

What is code-to-doc mapping for Next.js app and pages router references?

Code-to-doc mapping identifies affected documentation from code changes and maps them to the correct MDX pages, ensuring Next.js app and pages router references accurately reflect current features and APIs.

Does Next.js documentation require specific frontmatter for MDX pages?

Next.js documentation requires MDX pages to include proper title and description frontmatter, along with related links, following project conventions to ensure consistency across the documentation.

Can I automate documentation updates for new features in Next.js?

You can automate documentation updates for new features by using a repeatable PR workflow process that audits changes, scaffolds new docs, and validates content with linting rules.

What's the best way to validate Next.js MDX documentation after updates?

The best way to validate Next.js MDX documentation is to enforce validation steps such as lint checks and consistency verification with documentation conventions after mapping code changes.