release

Assess release readiness and generate versioned changelogs from git history.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/vsokh/maestro --skill release-vsokh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/vsokh/maestro/tree/main/.claude/skills/release
Command: npx skills add https://github.com/vsokh/maestro --skill release-vsokh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release helps teams reliably decide when to ship by assessing stability, enforcing release gates, generating user-facing changelogs, and managing semantic versioning without manual bookkeeping.

Core Features & Use Cases

  • Deterministic stability scoring from build/test results, codehealth metrics, fix ratios, backlog and regression signals.
  • Gate checks for build, tests, lint, codehealth, regressions and backlog with clear PASS/WARN/FAIL outcomes and remediation guidance.
  • Changelog generation, version bumping in package.json, annotated tagging, and writing structured release metadata and activity signals to .maestro.
  • Retroactive classification of legacy commits and milestone tagging to bootstrap historical release history.

Quick Start

Run the release status check to assess stability, preview the changelog, and review gate results before cutting a version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I generate a changelog and bump versions from git commit history?

You can assess release readiness by computing a deterministic stability score from build, test, lint, codehealth, fix ratios, and regression signals, providing clear PASS/WARN/FAIL gate outcomes.

What is a deterministic stability score for software releases?

A deterministic stability score evaluates release readiness by analyzing build and test results, codehealth metrics, fix ratios, backlog, and regression signals to reliably decide when to ship a version.

Can I use this release process with my Node.js package.json project?

Yes, the release process operates directly on Node.js projects by reading package.json, parsing git history, and utilizing .maestro quality artifacts to run gate checks and manage semantic versioning.

How do I enforce release gates for build, tests, and lint checks?

You enforce release gates by running available build, test, and lint commands, which produce clear PASS/WARN/FAIL outcomes with specific remediation guidance to block unstable releases.

What is the best way to bootstrap historical release tags for legacy commits?

The best way to bootstrap historical release history is retroactive classification of legacy commits and milestone tagging, which reconstructs past release events from existing git logs.

Why does my automated version bump fail when codehealth or regression gates fail?

Automated version bumping fails when gate checks detect regressions or poor codehealth, intentionally blocking the semantic version update and annotated tagging until remediation occurs.