codexkit-docs-shipper

To keep documentation in sync with code changes after a release, you identify and propagate updates triggered by product modifications to README, migration notes, and changelogs. This ensures shipped changes remain understandable across all relevant surfaces.

Generating changelogs and migration notes for a new release involves creating concise, structured entries that highlight what changed and why. Documentation updates are coordinated with templates and references to keep operator-facing docs aligned.

Yes, you can update operator-facing docs and README files simultaneously. The skill propagates documentation updates to all relevant surfaces, tailoring audience-specific prompts to reduce onboarding time for contributors and operators.

Frontmatter metadata in SKILL.md defines constraints that documentation updates must respect. The skill ensures updates are placed in the correct targets within the repository by adhering to this metadata during the propagation process.

You need to update release documentation across multiple repository targets when product or code changes trigger modifications. The skill coordinates these updates across README, changelogs, and operator-facing docs to maintain clarity after every release cycle.