create-release-note

You can auto-generate release notes from merged pull requests by deriving content from recent git tags and associated PRs within a specified version range. The Skill aggregates commits and classifies changes into categories like features, fixes, and docs.

The best way to structure release notes from git tags is to read predefined formatting rules from .agents/rules/release-commands.md. This classifies aggregated PR metadata into structured categories like features and fixes according to team conventions.

Yes, you need existing git tags to generate release notes for a versioned software project. The process requires access to git tags and PR metadata to define the version range and accurately derive the associated release content.

Yes, you can classify pull requests into features, fixes, and docs automatically. By reading predefined release-commands rules from .agents/rules/release-commands.md, the process categorizes merged PRs and formats the output based on your team conventions.

A key limitation of automating release note generation is the strict dependency on predefined rules in .agents/rules/release-commands.md for classification. Without proper git tags and structured PR metadata, the automated formatting may lack accurate context.