writing-release-notes

Release notes can be generated automatically by analyzing git commits and version files. This Skill reads your git history, detects version changes from files like package.json or Cargo.toml, categorizes commits by type (Added, Fixed, Changed, etc.), and outputs a formatted markdown changelog with dates and contributor references.

Yes. Conventional commits provide structured metadata that enables automatic categorization into sections like Added, Fixed, Deprecated, and Security. The Skill parses these commit messages alongside your git history to group related changes and generate well-organized release notes.

The Skill detects release types and version information by parsing package.json, pyproject.toml, Cargo.toml, and similar version files across different build ecosystems. It reads the current version to determine whether changes constitute a major, minor, or patch release.

Configure the Skill to run as part of your release workflow. It analyzes recent commits and version changes, then outputs a CHANGELOG or RELEASE_NOTES markdown file ready for distribution or deployment documentation without manual editing.

Yes. The Skill applies to software projects across languages and build ecosystems by analyzing git history and version files common to most projects—it doesn't depend on language-specific tooling, making it suitable for polyglot teams and monorepos.

Generated release notes include categorized sections for Added, Changed, Fixed, Deprecated, Removed, and Security changes. Each section groups related commits, includes dates, contributor references, and produces professional markdown formatted for immediate publication.