project-release

Automating GitHub releases with semantic versioning requires a workflow that enforces pre-release checks, applies version bump rules, updates CHANGELOG.md, and verifies GitHub release visibility. This skill standardizes that process to reduce human error and ensure consistent release hygiene.

Managing semantic versioning for multiple skills requires a standardized release workflow that defines when to bump MAJOR, MINOR, or PATCH versions based on changes. This skill provides version determination rules and a files update decision matrix to ensure consistent releases across all project components.

Creating a pre-release validation checklist for a GitHub workflow involves defining required steps like version bump verification, changelog updates, and file update decisions. This skill provides a formal pre-release checklist ensuring all required steps are completed before publishing a new release tag.

Post-release verification on GitHub confirms tag creation, release notes accuracy, and GitHub release visibility. This skill includes post-release verification as a core step to validate that the published release artifacts are correctly visible and formatted after the workflow completes.

Version bump rules dictate bumping MAJOR for breaking changes, MINOR for new features, and PATCH for bug fixes in an automated release workflow. This skill defines specific version determination rules to standardize when each semantic versioning level is applied based on project changes.

Updating README and CHANGELOG files during a release is handled through a files update decision matrix that guides which files require modifications. This skill provides that matrix to ensure all relevant documentation is updated consistently alongside the version bump and GitHub release publication.