merge-and-release

Automating GitHub PR merge and release workflows safely requires verifying approvals, status checks, and resolved conversations before merging, then calculating semantic version bumps and generating changelog notes with final human confirmation. This skill codifies those guardrails to prevent error-prone releases.

Enforcing PR approval and status check prerequisites before merging involves applying automated governance rules that block merges until required approvals, passing status checks, and resolved conversations are verified, preserving human confirmation for the final release execution.

Generating changelog and release notes from merged pull requests is handled by computing semantic version bumps based on merged changes and automatically producing release notes, which are then tagged and published upon final human confirmation.

Semantic versioning and changelog generation apply to standard repository release workflows where pull requests require approvals and checks. The process calculates version bumps and generates release notes while keeping human-in-the-loop confirmation for tier three release tagging tasks.

You need to provide the pull request number to start the merge and release process with all guardrails active. The skill then automatically verifies prerequisites, computes versioning, generates changelog notes, and awaits final human confirmation before tagging.

Automated release execution requires human confirmation because merge and release operations demand strict governance. Keeping a human-in-the-loop for tier three tasks like final tagging and publishing ensures correct versioning and prevents error-prone automated deployments.