document-release

Automate post-ship documentation updates by analyzing code diffs against core docs and applying precise, line-item changes. This synchronizes README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md to accurately reflect shipped changes and architecture decisions.

Synchronize contributor guidelines and project docs by running a post-ship workflow that cross-references shipped code diffs. It audits documentation drift and applies structured auto-updates while preserving changelog integrity and maintaining tone consistency.

Yes, you can audit README.md for documentation drift automatically. The workflow analyzes code diffs against the repository's core docs, identifies inconsistencies, and applies precise line-item changes to ensure documentation mirrors the latest shipped code.

Yes, the documentation sync workflow preserves changelog integrity during auto-updates. It applies structured changes to core docs while maintaining safety checks, per-file audits, and consistent tone across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE files.

Run a documentation diff analysis during release cycles where documentation must reflect code shipped, architecture decisions, and contributor guidelines. It ensures consistency across the project by auto-auditing diffs and updating core docs to mirror the latest changes.

Automated line-item doc updates apply precise changes to ARCHITECTURE.md based on code diffs, but require safety checks and per-file audits. Limitations include ensuring tone consistency and preserving changelog integrity while applying structured auto-updates across the project workflow.