release_authority

Name: release_authority
Availability: InStock
Author: idandavidaviv

Automates software release governance with strict versioning, changelog and artifact checks.

2|Updated Mar 26, 2026

Search Tags:#automation #git #versioning #audit #release #ci-cd

Ready to run

npx skills add https://github.com/IdanDavidAviv/virgo --skill release-authority

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release_authority
Source: https://github.com/IdanDavidAviv/virgo/tree/main/.agent/skills/release_authority
Command: npx skills add https://github.com/IdanDavidAviv/virgo --skill release-authority

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Unified Release Authority — Single Source of Truth for all release lifecycle actions. Merges release_prestige and version_sentinel into one sovereign skill covering: semantic versioning rules, authorization gates, pipeline execution, artifact verification, git history auditing, SemVer enforcement, and post-release validation.

Core Features & Use Cases

Consolidates governance and automation of release lifecycles across packages.
Enforces version parity, changelog hygiene, and auditable gatekeeping for each release.
Supports deterministic packaging, verification, and post-release validation workflows.

Quick Start

Initiate the end-to-end release workflow by auditing, bumping the version, updating the changelog, and pushing the release artifacts.

Frequently Asked Questions about release_authority

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

FAQPage Schema

How do I enforce semantic versioning and changelog updates before a CI-CD release?▼

To enforce semantic versioning and changelog updates before a release, you need an automated governance workflow that checks version parity and requires strict changelog modifications prior to pipeline execution.

What is the best way to audit git history for multi-package software releases?▼

Auditing git history for multi-package software releases requires an automated release authority workflow that consolidates gatekeeping, SemVer enforcement, and version control into a single enforceable pipeline.

How do I prevent misconfigured or unauthorized artifact deployments in my release pipeline?▼

To prevent misconfigured or unauthorized artifact deployments, implement deterministic packaging and artifact verification workflows that validate artifacts against strict version control and release authorization gates.

Can I automate post-release validation and version parity checks across multiple packages?▼

Yes, you can automate post-release validation and version parity checks across multiple packages by applying a unified release lifecycle skill that orchestrates verification workflows and enforces SemVer rules.

Does this release governance workflow work without external dependencies?▼

Yes, this release governance workflow operates entirely through internal scripts without external dependencies, providing deterministic artifact verification, git history auditing, and changelog discipline for multi-package projects.