sync-docs-from-diff

This skill synchronizes project documentation with code changes by analyzing git diffs between a base branch and HEAD, generating non-destructive patch proposals for your root README, docs directory, and inline markdown files for review.

The best way to sync project documentation after merging a feature branch is to analyze the code diffs and generate proposed updates for the README, docs folder, and inline code docs, reviewing each change before applying only the approved modifications to eliminate outdated docs.

Yes, you can update only the root README because the workflow supports partial re-runs for specific documentation areas, allowing you to target individual sections without restarting the entire synchronization process.

Yes, you need a valid Git repository with a detectable base branch to generate documentation patch proposals, as the diff-based analysis relies on comparing your current HEAD against a base branch to identify code changes requiring doc updates.

Generating documentation updates does not modify your original files because the tool creates non-destructive patch proposals for three distinct doc areas, enabling you to safely review all proposed changes and perform post-application validation before applying any updates.

Your documentation synchronization process might not resume because it requires using the supported resumable sessions feature, which allows interrupted work to continue without restarting, ensuring partial re-runs for specific doc areas like the README or docs directory are properly tracked.