release

Automate production releases for CRL-Web using Git and GitHub APIs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chrisbruceus/URL-Streamer --skill release-chrisbruceus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/chrisbruceus/URL-Streamer/tree/main/.github/skills/release
Command: npx skills add https://github.com/chrisbruceus/URL-Streamer --skill release-chrisbruceus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating production releases by automating version bumping, git tagging, and GitHub Release creation, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • Automated Versioning: Manages semantic versioning (MAJOR.MINOR.PATCH) based on commit history.
  • Git Tagging & Pushing: Creates and pushes annotated git tags for new releases.
  • GitHub Release Creation: Generates release notes from commit messages and creates a GitHub Release.
  • Use Case: When a set of new features and bug fixes are ready for production, you can trigger this skill to tag the release, generate a changelog, and publish it on GitHub, which in turn can trigger a production deployment.

Quick Start

Use the release skill to create a production release for the CRL-Web repository.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub releases with semantic versioning from commit history?

Automating GitHub releases involves parsing commit history to determine semantic version bumps, creating annotated git tags, and publishing a GitHub Release with auto-generated release notes. This eliminates manual versioning errors and standardizes deployment tagging.

How does semantic versioning work when generating git tags for production deployment?

Semantic versioning for git tags works by analyzing commit messages to increment MAJOR, MINOR, or PATCH versions appropriately. It then creates an annotated git tag reflecting this new version number to mark the specific deployment state in the repository.

Do I need the gh CLI installed to create and push git tags to GitHub?

Yes, you need the gh CLI installed and configured. The Skill relies on the GitHub API through the gh command-line tool to create annotated git tags, generate release notes, and publish the final GitHub Release to your repository.

Can I generate GitHub release notes automatically from my commit messages?

Yes, release notes can be generated automatically from your commit history. The Skill aggregates commit messages since the last tag to compile a changelog, which is then attached to the newly created GitHub Release for clear deployment documentation.

What is the best way to handle a hotfix release and rollback a production deployment?

For a hotfix release, the Skill manages an expedited semantic version bump and creates a new annotated git tag. It also provides rollback guidance to help you revert to the previous stable tag if the hotfix deployment fails.