update-docs

Documentation drift occurs when code changes are not reflected in docs. This Skill scans dependency manifests and file paths to perform a diff analysis, proposing precise edits to align README and CONTRIBUTING files with the current codebase.

You can automate documentation updates for multiple locales by performing a diff-driven scan of your project's current versioned states. This process identifies outdated content and proposes structured edits across all localized docs to maintain consistency.

Diff analysis for documentation syncing identifies mismatches between your codebase and docs by comparing versioned states. You need this process when frequent code changes cause documentation drift, increasing onboarding friction for new contributors.

Yes, you can track documentation changes aligned with code versions for consistent releases. The process maintains a verifiable audit trail of edits made to README and other docs, ensuring structured governance over project documentation updates.

Automated docs syncing is optimized for projects with dependency manifests and versioned states. Without these inputs, the diff analysis may lack the necessary context to accurately identify documentation drift or propose precise edits to your files.