update-docs

To automatically update documentation from code changes, map git diffs from your active branch to relevant documentation pages and generate updates. This aligns docs with code by proposing changes automatically and reducing manual rework.

Keep Next.js API references in sync during PR reviews by mapping code diffs to surface missing sections and outdated references. This validates frontmatter correctness, markdown structure, and cross-links to ensure docs stay consistent.

Documentation drift occurs when docs become outdated relative to code. Prevent drift by automatically identifying code changes and proposing required documentation updates, enforcing frontmatter and markdown structure validation during maintenance.

Yes, you can validate markdown cross-links and frontmatter automatically. The update process enforces frontmatter correctness, validates content structure, and checks cross-links to ensure documentation stays consistent with code changes.

The best way to map git diffs to architecture docs is analyzing the diff to identify changed source files, mapping those changes to relevant documentation pages, and applying updates with structural validation.

Yes, this documentation workflow works without external dependencies. It independently analyzes git diffs, maps changes to documentation pages, and enforces validation rules without requiring additional lint or documentation tools.