Skip to content
OpenSmartRoute
Skillv1.0.0

release-orchestrator

Orchestrate end-to-end release pipelines. Use when running pre-release validation, generating changelogs, bumping semantic versions, scoring deployment readiness, or gating releases with secret scanni

by borghei(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from borghei/claude-skills (engineering/release-orchestrator/SKILL.md). Install upstream with npx skills add borghei/claude-skills --skill release-orchestrator. Copyright stays with the author (MIT + Commons Clause).

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.

Core Capabilities

  • Pre-flight validation — 7 automated checks: branch sync, merge conflicts, dirty tree, secret scanning (AWS/GCP/GitHub/Stripe/JWT), gitignore coverage, conventional commits, dependency lock consistency.
  • Version management — auto-detect semver bump (PATCH/MINOR/MAJOR) from commit history across package.json, pyproject.toml, Cargo.toml, etc.; pre-release tags (--pre alpha|beta|rc).
  • Changelog generation — Keep a Changelog markdown grouped by type (Added/Changed/Fixed/Security/Breaking) with hashes and @author attribution.
  • Deployment readiness — weighted score across 7 categories (Tests, Code Quality, Docs, Security, Breaking Changes, Dependencies, Rollback) → GO (80+) / CONDITIONAL (60-79) / NO-GO (<60), with single-category blocker at <40.
  • End-to-end pipeline — chain all tools non-interactively; blocks on pre-flight failure, test failure, or NO-GO. CI/CD steps and pre-push git hook provided.
  • Release types — hotfix, patch, minor, major, and pre-release flows with branch patterns and bump rules.

When to Use

  • Running pre-release validation or gating a release with secret scanning and GO/NO-GO checks.
  • Generating a changelog from conventional commits before tagging.
  • Auto-bumping a semantic version from commit history.
  • Scoring deployment readiness across tests, quality, security, and rollback.
  • Wiring release validation into a CI/CD pipeline or pre-push hook.

Clarify First

Before orchestrating the release, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Base branch & ref range — what HEAD is compared against (drives pre-flight branch-sync and the changelog --from/--to)
  • Release type — hotfix / patch / minor / major / pre-release (sets the branch pattern and bump rule)
  • Gate strictness — block on CONDITIONAL (60-79) or only on NO-GO (<60) (decides whether the pipeline halts)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

Tool Purpose Command
preflight_checker.py Run 7 pre-release checks (sync, conflicts, secrets, commits, deps) python scripts/preflight_checker.py --repo . --base main --json
changelog_generator.py Generate Keep a Changelog markdown from a ref range python scripts/changelog_generator.py --repo . --from v1.2.0 --to HEAD --output CHANGELOG.md
version_bumper.py Auto-detect next semver from commits; write version files python scripts/version_bumper.py --repo . --dry-run --json
release_readiness_scorer.py Score readiness 0-100 with GO/CONDITIONAL/NO-GO decision python scripts/release_readiness_scorer.py --input release_data.json --json

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

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/release-workflows-and-operations.md — quick-start commands, the three core workflows (pre-flight, version/changelog, readiness) with their checkpoint tables, the end-to-end pipeline script, release-type matrix, CI/CD integration YAML, anti-patterns, and the troubleshooting table. Read when running or chaining any workflow.
  • references/release_engineering_guide.md — release strategies (rolling, blue-green, canary) and release engineering practice. Read when choosing a deployment strategy.
  • references/rollback_strategies.md — database migration rollbacks, reversible-migration rules, and rollback playbooks. Read when planning the rollback portion of a release.
  • references/ci_cd_best_practices.md — pipeline design patterns (stage-gate, fan-out/fan-in) and CI/CD best practices. Read when designing the surrounding pipeline.

Scope & Limitations

This skill covers: pre-flight validation, semantic version bumping, changelog generation, deployment-readiness scoring, and gating releases with GO/NO-GO decisions for git + conventional-commits projects.

This skill does NOT cover: the actual deploy/orchestration execution (handled by senior-devops / devops-workflow-engineer), test authoring (senior-qa), or deep security scanning beyond secret pattern-matching (senior-secops).

Integration Points

Skill Integration
senior-devops Pipeline stages consume pre-flight and readiness JSON as gates
senior-qa Test results feed Tests category (25% weight)
senior-secops Secret scan and CVE counts feed Security category (15%)
code-reviewer Code quality metrics feed Code Quality category (20%)
devops-workflow-engineer Workflow YAML calls tools as pipeline steps

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/borghei-claude-skills-release-orchestrator/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

borghei-claude-skills-release-orchestrator.ocm.jsonjson
{
  "ocm": "1",
  "id": "borghei-claude-skills-release-orchestrator",
  "kind": "skill",
  "name": "release-orchestrator",
  "description": "Orchestrate end-to-end release pipelines. Use when running pre-release validation, generating changelogs, bumping semantic versions, scoring deployment readiness, or gating releases with secret scanning and GO/NO-GO checks.",
  "publisher": "borghei",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "release-pipeline",
      "versioning",
      "pre-flight",
      "readiness",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Orchestrate end-to-end release pipelines. Use when running pre-release validation, generating changelogs, bumping semantic versions, scoring deployment readiness, or gating releases with secret scanning and GO/NO-GO checks."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/borghei/claude-skills",
      "path": "engineering/release-orchestrator/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/borghei/claude-skills/blob/HEAD/engineering/release-orchestrator/SKILL.md",
      "key": "borghei/claude-skills/engineering/release-orchestrator/SKILL.md"
    },
    "license": "MIT + Commons Clause"
  },
  "instructions": "# Release Orchestrator\n\nThe 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.\n\n## Core Capabilities\n\n- **Pre-flight validation** — 7 automated checks: branch sync, merge conflicts, dirty tree, secret scanning (AWS/GCP/GitHub/Stripe/JWT), gitignore coverage, conventional commits, dependency lock consistency.\n- **Version management** — auto-detect semver bump (PATCH/MINOR/MAJOR) from commit history across `package.json`, `pyproject.toml`, `Cargo.toml`, etc.; pre-rel",
  "cost": {
    "context_tokens": 1297
  }
}

Fetch it by URL: GET /api/v1/registry/borghei-claude-skills-release-orchestrator/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.