generate-release-cc

Automate OmniRoute patch releases from version bump to gated deployment.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill generate-release-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-release-cc
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/generate-release-cc
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill generate-release-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the risk and manual effort of cutting OmniRoute releases by automating the version bump, security checks, and a complete CHANGELOG built from every commit since the last tag, then gating everything behind a user-approved pull request.

Core Features & Use Cases

  • Patch-only versioning with threshold rules: Ensures OmniRoute always releases using PATCH bumps and applies the special 1000-threshold rule for the y segment.
  • Release-branch integration workflow: Enforces a standardized release cycle where work lands on release/vX.Y.Z and is merged to main via a single final release PR.
  • Mandatory Phase 0 security verification: Runs dependency audit plus CodeQL and Dependabot high/critical alert checks before any release actions proceed.
  • Complete CHANGELOG generation: Produces an end-to-end CHANGELOG entry covering every commit since the last tag, grouped by Conventional Commit type, including PR back-references and contributor attribution.
  • Controlled deployments with explicit STOP points: Deploys to local VPS only after the PR is merged and passes; tags/releases/publishing happen only after explicit approvals.
  • Rollback playbook: Provides an immediate recovery procedure if Phase 3 launch causes a fatal regression after tagging.

Quick Start

Generate the next OmniRoute patch release by following the Phase 0 security verification, creating the release branch, bumping the version, generating the full CHANGELOG from commits since the last tag, committing, and opening a PR to main for user confirmation.

Frequently Asked Questions about generate-release-cc

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

FAQPage Schema
How do I automate semantic versioning and changelog generation for patch releases?

Automate semantic versioning and changelog generation by bumping the PATCH version, applying y-threshold logic, and assembling an end-to-end changelog from every commit since the last tag grouped by Conventional Commit type.

Can I enforce security verification and CI quality gates before a deployment workflow proceeds?

Security verification and CI quality gates are enforced during a mandatory Phase 0 that runs dependency audits plus CodeQL and Dependabot high and critical alert checks before any release branch actions proceed.

How do I create a release integration branch and gate deployments with a pull request?

Create a release integration branch to standardize work and gate deployments by opening a single final pull request to main, enforcing explicit user-approval STOP points before tagging, publishing, and local VPS deployment.

Does the release workflow support rollback if a deployment causes a fatal regression?

The release workflow supports rollback by providing an immediate recovery procedure playbook to follow if a Phase 3 launch causes a fatal regression after tagging and deployment.

What is the best way to keep OpenAPI documentation synced during a release cycle?

Keep OpenAPI documentation synced during a release cycle by automatically updating doc version sync as part of the version bump and controlled publishing steps to main, Docker, and npm environments.