release-manager

You can automate changelog validation and release note drafting by running this skill to identify version changes, verify consistency against actual code changes, and generate notes. It requires access to your repository's commit history, CI status, and release configuration.

Verifying semantic versioning compliance involves checking that your version bump aligns with Semver principles based on actual code changes. This skill automates that verification alongside CI status checks to ensure your repository is in a ready-to-publish state.

Checking if your CI workflow is ready for a repository release involves validating the CI status and release workflow configuration. This skill automates these checks, confirming that all necessary pre-release steps are completed successfully before publication.

Yes, you can use release management tools to validate consistency between commits and changelog entries. This skill specifically checks for alignment between your changelog documentation and the actual code changes identified in your repository's commit history.

Before automating software release preparation, you need to ensure access to your repository's commit history, CI status, and release configuration. These inputs allow the skill to identify version changes, verify Semver compliance, and draft accurate release notes.

Release workflow validation fails when changelog entries are missing because the skill checks for strict consistency between your changelog and actual code changes. Updating the changelog to reflect all identified version changes resolves this validation block.