update-docs

You can update documentation by analyzing code diffs to map changes to existing markdown files, then applying guided edits or scaffolding new API reference pages to keep content fully synced with your Next.js codebase.

Keeping API reference docs in sync is handled by analyzing pull request code modifications, identifying impacted documentation files, and generating new reference entries that adhere to your established project conventions.

Yes, you can scaffold new documentation by evaluating feature types from your code changes and creating new markdown files structured as guides or API references based on the identified modifications.

Yes, the workflow supports both API reference generation and guide creation by mapping code changes to documentation files and applying updates or scaffolding new entries that follow established conventions.

Using code diffs to drive documentation updates relies on established conventions and clear code modifications, meaning heavily refactored logic without explicit diffs may require manual mapping to ensure complete markdown content alignment.