Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Release Orchestrator

  • 73 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

Release Orchestrator is a Claude skill that runs pre-flight release validation, semantic-version bumping, changelog generation and deployment-readiness scoring with a GO/CONDITIONAL/NO-GO decision.

About

Release Orchestrator runs pre-flight validation, generates changelogs from conventional commits, auto-bumps semantic versions and scores deployment readiness with a GO/CONDITIONAL/NO-GO decision. A developer uses it to gate a release: check branch sync, scan for secrets, verify conventional commits and lock files, then produce a version bump, changelog and readiness score. It ships four CI-friendly Python tools and chains them into an end-to-end pipeline.

  • 7-check pre-flight: branch sync, conflicts, secrets, commits, deps
  • Semver auto-bump from conventional commits and Keep-a-Changelog generation
  • Deployment readiness score with GO / CONDITIONAL / NO-GO gating

Release Orchestrator by the numbers

  • 73 all-time installs (skills.sh)
  • Ranked #129 of 248 Release Management skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

release-orchestrator capabilities & compatibility

Capabilities
release notes · pr review expert · ci cd pipeline
Works with
github
Use cases
ci cd · devops · security audit
Pricing
Free
From the docs

What release-orchestrator says it does

Use when running pre-release validation, generating changelogs, bumping semantic versions, scoring deployment readiness, or orchestrating end-to-end release pipelines.
SKILL.md
The agent runs seven automated checks:
SKILL.md
Any single category below 40 triggers a mandatory blocker regardless of overall score.
SKILL.md
npx skills add https://github.com/borghei/claude-skills --skill release-orchestrator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs73
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

What it does

Run pre-flight checks, auto-bump semver, generate changelogs and score deployment readiness with a GO/CONDITIONAL/NO-GO decision.

Who is it for?

Gating a release with pre-flight checks, semver bump, changelog and a readiness decision.

Skip if: Writing customer-facing release copy (use release-notes) or reviewing an individual PR.

When should I use this skill?

Running pre-release validation, bumping versions, generating a changelog, or scoring deployment readiness.

What you get

A validated, versioned release with a changelog and a scored GO/CONDITIONAL/NO-GO deployment decision.

  • pre-flight report
  • version bump
  • changelog

By the numbers

  • 7 pre-flight checks
  • 4 Python tools
  • 7 weighted readiness categories

Files

SKILL.mdMarkdownGitHub ↗

Release Orchestrator

The agent runs pre-flight validation, generates changelogs from conventional commits, auto-bumps semantic versions, and scores deployment readiness with a GO/CONDITIONAL/NO-GO decision.

---

Quick Start

# Pre-flight: branch sync, secrets, conflicts, commits, deps
python scripts/preflight_checker.py --repo . --base main --verbose

# Changelog from conventional commits
python scripts/changelog_generator.py --repo . --from v1.2.0 --to HEAD

# Auto-detect version bump from commit history
python scripts/version_bumper.py --repo . --dry-run

# Score deployment readiness (7 categories, weighted)
python scripts/release_readiness_scorer.py --input release_data.json --json

Tools Overview

ToolInputOutput
preflight_checker.pyRepo path + base branchPass/fail on 7 checks (sync, conflicts, secrets, commits, deps)
changelog_generator.pyGit repo + ref rangeKeep a Changelog markdown with commit grouping
version_bumper.pyRepo pathNext semver from commit analysis; updates version files
release_readiness_scorer.pyRelease data JSONScore 0-100, GO/CONDITIONAL/NO-GO decision

All tools support --json for machine output. Exit code 0 = pass, 1 = fail (CI-friendly).

---

Workflow 1: Pre-Flight Validation

python scripts/preflight_checker.py --repo . --base main --json

The agent runs seven automated checks:

1. Branch sync -- local branch up to date with remote base 2. Merge conflicts -- dry-run merge to detect conflicts 3. Uncommitted changes -- fail if working tree is dirty 4. Secret scanning -- pattern-match for API keys, tokens, passwords (AWS, GCP, GitHub, Stripe, JWT) 5. Gitignore validation -- .env, credential files covered 6. Conventional commits -- recent commits follow type(scope): description 7. Dependency audit -- lock file consistency (package-lock.json, poetry.lock, etc.)

Validation checkpoint: All 7 checks pass. Exit code 0.

---

Workflow 2: Version Management and Changelog

Step 1 -- Auto-detect version bump.

python scripts/version_bumper.py --repo . --dry-run --json
Commit TypeBumpExample
fix:PATCH (0.0.x)fix(auth): handle expired tokens
feat:MINOR (0.x.0)feat(api): add pagination
feat!: or BREAKING CHANGEMAJOR (x.0.0)feat!: redesign auth flow
docs:, chore:, test:No bumpdocs: update README

Reads from: package.json, pyproject.toml, setup.py, setup.cfg, Cargo.toml, VERSION file. Pre-release support: --pre alpha|beta|rc produces 1.3.0-rc.1.

Step 2 -- Generate changelog.

python scripts/changelog_generator.py --repo . --from latest --to HEAD --output CHANGELOG.md --full

Groups commits by type (Added, Changed, Fixed, Security, Breaking Changes) with hashes and @author attribution.

Step 3 -- Apply version bump.

python scripts/version_bumper.py --repo .  # writes to all discovered version files

Validation checkpoint: --dry-run shows expected version. Changelog covers 100% of commits.

---

Workflow 3: Deployment Readiness

python scripts/release_readiness_scorer.py --input release_data.json --json

The agent scores across 7 weighted categories:

CategoryWeightMeasures
Tests25%Pass rate, coverage, flaky count
Code Quality20%Lint errors, type errors, complexity, duplication
Documentation15%README, API docs, changelog, migration guide
Security15%No secrets, no critical CVEs, SAST clean
Breaking Changes10%Documented, migration path, deprecation notices
Dependencies10%Lock files consistent, no yanked packages
Rollback Plan5%Procedure documented, DB migration reversible, feature flags

Decision thresholds:

ScoreDecisionAction
80-100GOProceed with deployment
60-79CONDITIONALProceed with mitigations documented
0-59NO-GOAddress blockers first

Any single category below 40 triggers a mandatory blocker regardless of overall score.

Validation checkpoint: Score >= 80 (GO). Zero category blockers.

---

End-to-End Release Pipeline

Chain all workflows into a single automated pipeline:

#!/bin/bash
set -e

# Phase 1: Pre-flight
python scripts/preflight_checker.py --repo . --base main --json > /tmp/preflight.json

# Phase 2: Tests (project-specific)
python -m pytest --cov=src --cov-report=json:coverage.json -v

# Phase 3: Version bump (dry-run)
python scripts/version_bumper.py --repo . --dry-run --json > /tmp/version.json

# Phase 4: Changelog
python scripts/changelog_generator.py --repo . --from latest --to HEAD

# Phase 5: Readiness assessment
python scripts/release_readiness_scorer.py --input release_data.json --json > /tmp/readiness.json
DECISION=$(python -c "import json; print(json.load(open('/tmp/readiness.json'))['decision'])")
echo "Decision: $DECISION"

Non-interactive by default. Blocks on: pre-flight failure, test failure, or NO-GO readiness.

---

Release Types

TypeBranch PatternBumpNotes
Hotfixhotfix/v1.2.1 from tagPATCHMinimal fix, branches from release tag
PatchStandard flowPATCHAccumulated bug fixes
MinorStandard flowMINORNew features, backward compatible
MajorStandard flowMAJORBreaking changes, needs migration docs
Pre-releaseStandard flow`--pre alpha\beta\

---

CI/CD Integration

- name: Pre-flight Check
  run: python scripts/preflight_checker.py --repo . --base main --json > preflight.json

- name: Version Bump
  run: python scripts/version_bumper.py --repo . --dry-run --json > version.json

- name: Changelog
  run: python scripts/changelog_generator.py --repo . --from latest --to HEAD --output CHANGELOG.md

- name: Readiness Score
  run: python scripts/release_readiness_scorer.py --input release_data.json

Git hook: python scripts/preflight_checker.py --repo . --base main in .git/hooks/pre-push.

---

Anti-Patterns

1. Skipping pre-flight -- secrets ship to production. Always run pre-flight before any release work. 2. Manual version bumping -- leads to inconsistencies. Let commit history drive the version. 3. No rollback plan -- every release needs documented rollback (git revert, feature flags, or DB migration down). 4. Ignoring single-category blockers -- a 95 overall score with 35 Security = NO-GO. 5. Changelog after release -- generate before tagging so reviewers can validate.

---

Troubleshooting

ProblemCauseSolution
Pre-flight "HEAD is detached"CI checked out specific commitCheck out a named branch first
Changelog "No commits found"--from ref does not existVerify tag with git tag -l; use --since date range
Version bumper cannot parse versionNon-semver format (e.g., 1.0)Use MAJOR.MINOR.PATCH in all manifest files
Readiness scorer exits 1 despite high scoreSingle category below 40-point blockerCheck BLOCKERS section; fix failing category
Secret scan false positives on test fixturesPattern matches example tokensLines with "example"/"placeholder" are skipped; move fixtures to non-tracked dir

---

References

GuidePath
Release Engineering Guidereferences/release_engineering_guide.md
Rollback Strategiesreferences/rollback_strategies.md
CI/CD Best Practicesreferences/ci_cd_best_practices.md

---

Integration Points

SkillIntegration
senior-devopsPipeline stages consume pre-flight and readiness JSON as gates
senior-qaTest results feed Tests category (25% weight)
senior-secopsSecret scan and CVE counts feed Security category (15%)
code-reviewerCode quality metrics feed Code Quality category (20%)
devops-workflow-engineerWorkflow YAML calls tools as pipeline steps

---

Last Updated: April 2026 Version: 2.1.0

Related skills

FAQ

What does the pre-flight checker validate?

Seven checks: branch sync, merge conflicts, uncommitted changes, secret scanning, gitignore validation, conventional commits and dependency audit.

How is the deployment readiness decision made?

A 0-100 score across 7 weighted categories maps to GO (80-100), CONDITIONAL (60-79) or NO-GO (0-59), with any category below 40 triggering a mandatory blocker.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.