release

To automate GitHub releases, the Skill gathers commit logs, composes changelog notes, creates version tags, and publishes the release end-to-end. It streamlines pushing versions to Git by reducing manual steps and errors across local repos or CI pipelines.

Generating a changelog from commit history is handled by compiling a cohesive summary of commits and diffs. The Skill automates this release notes generation process, ensuring formal versioning documentation is created directly from the repository's development history.

Yes, you need a Git environment with access to create tags. The Skill requires local or CI pipeline Git access to verify the target version tag does not already exist before composing notes, tagging, and publishing the GitHub release.

Yes, you can use this to publish GitHub releases within CI pipelines. The Skill applies to software projects requiring formal versioning and release assets, automating the end-to-end process of gathering logs, tagging, and publishing across automated environments.

The release process requires the target version tag to not already exist to prevent duplicate versions. The Skill ensures formal versioning integrity by verifying tag availability in the Git environment before proceeding with note composition and GitHub release creation.