update-doc

To keep documentation in sync with codebase updates, scan your repository to detect outdated sections, check for feature flags and duplicates, and use the guided approval workflow to apply targeted edits only where needed.

Detecting outdated pages in MDX documentation involves scanning the source code to surface discrepancies between the docs and the current implementation, checking for duplicates, and proposing precise updates to align the content.

Yes, you can review documentation changes before they are applied. The workflow enforces an approval step where you review the proposed targeted edits to signatures and examples before applying changes.

You generate targeted doc edits by aligning docs with current source code, which creates a change plan for signatures and examples, ensuring updates apply only to sections needing synchronization.

Yes, the documentation update workflow preserves existing prose and context by enforcing an approval step before applying changes, ensuring updates align with the codebase without overwriting valid content.

Avoid automated documentation sync when preserving manual prose context is critical without review, as the workflow applies changes only after an approval step to prevent unwanted content modifications.