write-release-notes

Automating release notes from git commits involves analyzing commit history, PR dependency graphs, and Terraform impact to generate a categorized draft. The skill creates a Linear tracking issue for owner sign-off before finalizing user-ready release notes.

Generating release notes with Terraform impact analysis requires parsing git commits and PR graphs to document infrastructure changes. This approach enforces version identification and categorizes changes into Notable Changes, Features, Enhancements, and Bug Fixes.

Categorizing changelog entries for minor and patch releases groups changes into Notable Changes, Features, Enhancements, and Bug Fixes. This version-aware formatting ensures user-ready release notes by structuring commits and PR context coherently.

Linear integration supports release note owner confirmation by creating and tracking issues for sign-off before writing. It enforces owner validation steps after analyzing git commits, Terraform impact, and customer feedback to produce the draft.

You can use customer feedback to draft release notes automatically by combining it with git commits, PR dependency graphs, and Terraform impact analysis. The process generates a coherent draft pending owner confirmation before final writing.

Providing previous and target version context is needed for release note generation to enforce version identification and apply version-aware formatting. It determines whether to apply minor or patch release categorization to the analyzed commits and PR graphs.