skills.rest
mkrlabs
mkrlabsOFFICIAL
Explore all skills by this author →
Website𝕏@MakerLabsDevGitHub

github-release

Automate GitHub releases with tag validation and build checks.

Updated Apr 22, 2026
Search Tags:#automation#github#release#ci-cd#cloud-build#artifact-registry
One-click install
npx skills add https://github.com/mkrlabs/specflow --skill github-release-mkrlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-release
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/github-release
Command: npx skills add https://github.com/mkrlabs/specflow --skill github-release-mkrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, gcloud, and includes scripts (resource) components.

What problem does it solve?

GitHub Release automation with tag validation, Cloud Build status verification, image existence checks, and automatic release notes generation to ensure releases are accurate and traceable.

Core Features & Use Cases

  • End-to-end release orchestration: resolves latest tag, validates tag, checks build and image status, and creates GitHub Release.
  • Release notes generation: compiles changes since previous tag and attaches to the release.
  • Deployment visibility: surfaces deploy workflow URL and status after release.

Quick Start

Run the release.sh script to create a GitHub release for the latest tag.

Frequently Asked Questions about github-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub releases with tag validation and release notes?▼

Automate GitHub releases by running a script that resolves the latest tag, validates it, checks Cloud Build status, verifies container images in Artifact Registry, and creates a release with generated notes.

How does release orchestration verify container images before publishing a GitHub release?▼

Release orchestration verifies container images by checking Artifact Registry for image availability, ensuring the tagged commit has a built and registered image before safely creating the GitHub release.

Do I need gcloud and gh CLI installed to automate end-to-end GitHub releases?▼

Yes, you need gcloud and gh CLI installed along with git to automate end-to-end GitHub releases, as the orchestration script depends on these tools for Cloud Build checks and release creation.

What is the best way to generate release notes from tagged commits in a CI/CD workflow?▼

Generate release notes from tagged commits in a CI/CD workflow by compiling changes since the previous tag, then attaching those detailed notes automatically to the newly created GitHub release.

Why does my GitHub release automation fail if a Cloud Build status check is not completed?▼

GitHub release automation fails if a Cloud Build status check is not completed because the orchestration implements guardrails that require build verification before proceeding with release creation.

Can I see deployment workflow status and URL after creating a GitHub release?▼

Yes, you can see deployment workflow status and URL after creating a GitHub release, as the automation surfaces deploy visibility by providing the workflow URL and checking its status post-release.

Related Skills

Explore More Software Engineering Skills→
labringlabring
69

sealos-deploy

Deploy GitHub repositories and local projects to Sealos Cloud.

Official
Advanced
oogDZoogDZ

post-release

Validate GitHub Release notes, CHANGELOG updates, and deployment statuses after publication.

Community
Intermediate
nccasianccasia

github-actions-templates

Create GitHub Actions workflows for CI/CD testing, Docker builds, Kubernetes deployment, and security scanning.

Official
Intermediate
d-o-hubd-o-hub
11

github-workflows-release-management

Diagnose, fix, and optimize GitHub Actions workflows for Rust CI/CD pipelines.

Community
Advanced