GitHub Release Workflow

Automate GitHub release workflows with pre-release checks, branch creation, version updates, and tagging.

Updated Dec 6, 2025
One-click install
npx skills add https://github.com/sanruiz/fibra --skill github-release-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitHub Release Workflow
Source: https://github.com/sanruiz/fibra/tree/main/.github/skills/github-release-workflow
Command: npx skills add https://github.com/sanruiz/fibra --skill github-release-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable release process for the SOMA theme, ensuring version bumps, changelog accuracy, and production deployment readiness.

Core Features & Use Cases

  • Pre-release checks: validates PHPCS, PHPStan, tests, and frontend build before release.
  • Release orchestration: creates release branches, updates version files (style.css and CHANGELOG), and automates changelog updates.
  • PR and tagging: opens a labeled PR to main and creates an annotated release tag after merge.
  • Deployment monitoring: tracks CI/CD deployment progress and confirms production readiness.

Quick Start

Follow the pre-release checks, create a release branch from develop, update version files and changelog, and open a labeled PR to main to begin the release.

Frequently Asked Questions about GitHub Release Workflow

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

FAQPage Schema
How do I automate a GitHub release workflow with quality gates?

A GitHub release workflow automates versioning, changelog updates, and deployment readiness. It validates quality gates like PHPCS, PHPStan, and frontend builds before creating a labeled PR and tagging the release from main.

What is the process to update version files and changelogs for a GitHub release?

Updating version files and changelogs involves creating a release branch, bumping versions in style.css, and automating changelog entries. This skill handles those updates before opening a labeled PR to main for merge.

When do I need to create an annotated release tag in a CI/CD pipeline?

You need an annotated release tag after a labeled PR merges to main. This skill ensures tagging originates deterministically from main post-merge to guarantee production deployment readiness and accurate version tracking.

Does this GitHub release workflow support PHPStan and PHPCS pre-release checks?

Yes, this GitHub release workflow validates quality gates including PHPCS, PHPStan, tests, and frontend builds. These pre-release checks are enforced before release branch creation to ensure code quality.

What is the best way to monitor deployment progress after a GitHub release?

The best way to monitor deployment progress is tracking CI/CD pipeline execution after tagging. This skill monitors deployment progress and confirms production readiness once the release workflow completes.