generate-release-cx

Automates OmniRoute patch releases with changelog generation and PR management.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky, inconsistent OmniRoute releases by standardizing version bumps, security checks, and release documentation into one guarded workflow that requires human approval at key gates.

Core Features & Use Cases

  • End-to-end release orchestration: Creates/validates the correct release/vX.Y.Z integration branch flow, enforces patch-only versioning rules, and coordinates changelog generation from commits since the last tag.
  • Complete CHANGELOG with attribution: Builds a full CHANGELOG.md section including PR back-references, contributor attribution, and coverage assertions so no commit is silently omitted.
  • Safety gates and controlled publishing: Runs security verification (npm audit, CodeQL, Dependabot), enforces quality gates, and stops for user confirmation before deployment/tagging steps.

Quick Start

Run the release workflow with the Generate Release skill and follow its prompts to review the PR and approve Phase 2 and Phase 3 before any tagging or publishing occurs.

Frequently Asked Questions about generate-release-cx

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

FAQPage Schema
How do I automate generating a changelog from commits for a new release branch?

To automate changelog generation, this Skill extracts commits since the last tag, builds a complete CHANGELOG.md section with PR back-references and contributor attribution, and enforces coverage assertions so no commit is silently omitted.

What is the safest way to manage semantic versioning and pull requests for patch releases?

Managing semantic versioning safely involves standardizing patch version bumps and coordinating the pull request to main with staged approvals. This Skill enforces branch and version parity checks before allowing any merge or tag operations.

Can I enforce security auditing and quality gates before merging a release pull request?

Yes, you can enforce security auditing and quality gates before merging. The workflow mandates security scanning via npm audit, CodeQL, and Dependabot, halting for explicit user confirmation before proceeding to deployment or tagging phases.

How do I prevent unauthorized commits from being included in a production deployment?

Preventing unauthorized commits requires atomic commit rules and changelog coverage assertions. This Skill validates the release branch flow and stops for user confirmation at Phase 2 and Phase 3 before any tagging or publishing occurs.

What are the limitations of automating release preparation with CI quality gates?

A limitation of automating release preparation with CI quality gates is that the workflow enforces patch-only versioning rules and requires manual user confirmation at deployment, tagging, and publishing phases, preventing fully automated major version releases.