changelog-writing

To generate a structured changelog entry, this Skill consumes your latest completion-report and implementation-summary artifacts to produce a standardized changelog-entry artifact with explicit change_type classification and known_limitations disclosure.

Documenting breaking changes requires explicit breaking_changes disclosure within your changelog. This Skill enforces breaking_changes disclosure and provides migration paths by applying standardized change_type classification to your release artifacts.

Making versioning documentation compliant involves maintaining a Keep a Changelog compliant structure. This Skill automates structured changelog documentation by enforcing explicit change_type classification and known_limitations disclosure for every release.

The best way to classify release changes is by applying explicit change_type categories. This Skill automates classification into feature, repair, docs-only, and governance groups using your completion-report and implementation-summary artifacts.

Yes, this changelog automation works with readme-sync workflows. It ensures information consistency by producing structured changelog-entry artifacts that seamlessly connect with your documentation synchronization processes.

You should not use automated changelog generation when your release lacks complete completion-report or implementation-summary artifacts. The Skill relies on consuming these inputs to enforce accurate breaking_changes disclosure and classification.