release-check

Automate pre-release validation by running checks that verify repository status, branching, dependencies, and documentation to ensure software is ready for release. This reduces risk from missing checks and manual QA before publishing a new version.

Changelog validation ensures RELEASE_NOTES.md and CHANGELOG.md are present and consistent before release. It matters because maintaining accurate release documentation prevents publishing versions with missing or mismatched quality gate information.

Yes, you can run release checks on both main and release branches across projects. The validation applies to repositories preparing these branches to ensure version consistency, test results, and documentation checks pass.

Validate version consistency by executing a pre-release check that delivers deterministic checks with clear failure reasons. It provides actionable remediation guidance to fix any version or dependency inconsistencies before publishing.

When a pre-release quality gate fails, the validation delivers clear failure reasons and actionable remediation guidance. This deterministic approach helps maintainers identify and resolve repository, branching, or documentation issues quickly.

You do not need a specific continuous integration setup to validate documentation before release. The skill independently ensures release notes and changelog validation, applying comprehensive checks directly to the repository state.