draft-release-notes

Automating release notes requires a structured change list and target version to generate a categorized draft document. This skill scans changelog data and adapts the output format to match project conventions automatically.

Generating version control release documentation is handled by processing structured change data into a clean, categorized draft. The skill adapts the tone and conventions to match the project's specific voice for software release updates.

Automated release notes require a structured change list as input, typically sourced from a changelog scan. Providing organized change data ensures the generated draft accurately reflects software updates and adapts to project standards.

Customizing software release notes is supported by adapting the generated draft to match project voice and conventions. The skill processes structured change data to ensure the final documentation aligns with established formatting standards.

Creating a categorized draft release notes document involves inputting a structured change list and target version into the skill. It outputs an organized draft that simplifies preparing software development release documentation.

To automatically draft release notes, you must provide a structured change list and the target version. The skill uses this input to scan changelog data and produce a clean, categorized draft document.