update-docs

The Skill scans the git diff between main and HEAD, maps changed source files to their corresponding documentation pages using SOURCE_DOC_MAPPING.md, and applies precise edits to align the docs with your code changes.

Mapping changed source files to documentation pages works by reading the SOURCE_DOC_MAPPING.md file in your repository, which links specific source code paths to their corresponding MDX documentation sections for targeted updating.

Yes, you can sync MDX documentation files while preserving existing content. The process applies precise edits only to the touched sections mapped from the code diff, leaving the rest of the documentation page untouched.

The best way to maintain a docs branch tracking code changes is to automate the diff scan against main, map the modified sources to MDX pages, and apply minimal targeted edits to keep documentation synchronized.

Yes, you need a SOURCE_DOC_MAPPING.md file to automate documentation-sync across multiple services. It acts as the reference table linking changed source files to their corresponding documentation pages for accurate edits.

A limitation of applying targeted edits based on source control diffs is that the process requires a valid SOURCE_DOC_MAPPING.md file and only updates MDX documentation, preserving existing content solely for mapped sections.