Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
Orchestrate end-to-end release pipelines. An agent skill from borghei/Claude-Skills.
Install Release Orchestrator
$ npx skills add borghei/Claude-Skills --skill release-orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills release-orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/release-orchestrator .claude/skills/release-orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-orchestrator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestrator into .claude/skills/release-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill release-orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills release-orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/release-orchestrator .agents/skills/release-orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-orchestrator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestrator into .agents/skills/release-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill release-orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills release-orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/release-orchestrator .cursor/skills/release-orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-orchestrator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestrator into .cursor/skills/release-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/release-orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill release-orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills release-orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/release-orchestrator .gemini/skills/release-orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-orchestrator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestrator into .gemini/skills/release-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills release-orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill release-orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/release-orchestrator .github/skills/release-orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-orchestrator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestrator into .github/skills/release-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill release-orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills release-orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/release-orchestrator .opencode/skills/release-orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-orchestrator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-orchestrator into .opencode/skills/release-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-orchestrator- GitHub stars
- 881
- Token cost
- ~1.5k tokens
- SKILL.md length
- 564 words
- Files
- 11 (incl. scripts, references, assets)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Orchestrate end-to-end release pipelines. An agent skill from borghei/Claude-Skills.
- Running pre-release validation
- SKILL.md covers Core Capabilities, When to Use, Clarify First and Tools, plus 3 more sections
- Runs Python scripts from its folder; calls python
- Generating changelogs
What it does
Release Orchestrator is an agent skill from borghei/Claude-Skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `assets/release_checklist_template.md`, `assets/sample_release_data.json` and `references/ci_cd_best_practices.md`).
It sits in Development, covering Changelog and release notes, Secrets management and Feature launches and release readiness. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Running pre-release validation
- Generating changelogs
- Bumping semantic versions
- Scoring deployment readiness
Example prompts
- “/release-orchestrator”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Orchestrator loads about 1.5k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 564 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 564 words, ~1,464 tokens.
Download SKILL.mdSave it as
.claude/skills/release-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.- 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.
- license
- MIT + Commons Clause
- metadata.version
- 2.2.0
- metadata.author
- borghei
- metadata.category
- engineering
- metadata.domain
- release-engineering
- metadata.updated
- 2026-06-17
- metadata.tags
- release-pipeline, versioning, pre-flight, readiness
- metadata.python-tools
- preflight_checker.py, changelog_generator.py, version_bumper.py, release_readiness_scorer.py
- metadata.tech-stack
- python, git, semver, conventional-commits, ci-cd
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
@authorattribution. - 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).
Show full SKILL.md (199 more words)Show less
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 |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 10 other files (scripts, references, assets) in engineering/release-orchestrator of borghei/Claude-Skills.
- SKILL.md
- assets/release_checklist_template.md
- assets/sample_release_data.json
- references/ci_cd_best_practices.md
- references/release-workflows-and-operations.md
- references/release_engineering_guide.md
- references/rollback_strategies.md
- scripts/changelog_generator.py
- scripts/preflight_checker.py
- scripts/release_readiness_scorer.py
- scripts/version_bumper.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Release Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Orchestrator this skillborghei/Claude-Skills | 881 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Release Engineeringmajiayu000/spellbook | 286 | — | ~511 | Automated safety check: Pass | MIT | |
| Cline Desktop App Releasecline/cline | 70k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| EverOS Release WorkflowEverMind-AI/EverOS | 13k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Releasengrok/ngrok-operator | 272 | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Release Engineering
majiayu000/spellbook
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness.
Cline Desktop App Release
cline/cline
Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.
EverOS Release Workflow
EverMind-AI/EverOS
Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.
Release
ngrok/ngrok-operator
Automates the ngrok-operator release process: gathers PR data, classifies changes by component (container, Helm chart, CRDs chart), generates changelogs, updates version files, and prepares the…
Remotion Bits Release
av/remotion-bits
Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Release Orchestrator
What does Release Orchestrator do?
Orchestrate end-to-end release pipelines. An agent skill from borghei/Claude-Skills. Release Orchestrator is an agent skill from borghei/Claude-Skills. Orchestrate end-to-end release pipelines.
When should I use Release Orchestrator?
Release Orchestrator fits situations like: running pre-release validation; generating changelogs; bumping semantic versions; scoring deployment readiness.
How do I install Release Orchestrator in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill release-orchestrator -a claude-code`. Or copy the skill folder (engineering/release-orchestrator in borghei/Claude-Skills) into .claude/skills/release-orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Release Orchestrator in Codex?
Run `npx skills add borghei/Claude-Skills --skill release-orchestrator -a codex`. Or copy the skill folder (engineering/release-orchestrator in borghei/Claude-Skills) into .agents/skills/release-orchestrator in your project. Codex loads it when a task matches its description.
Can I use Release Orchestrator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill release-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-orchestrator, .gemini/skills/release-orchestrator, .github/skills/release-orchestrator and .opencode/skills/release-orchestrator in your project.
What does Release Orchestrator need to run?
Going by SKILL.md and its folder, Release Orchestrator needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Release Orchestrator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Orchestrator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Release Orchestrator use?
Release Orchestrator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Orchestrator use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.1k tokens, read only when the agent opens those files.
What are the alternatives to Release Orchestrator?
Skills that share tags, products or a category with Release Orchestrator: Release Maintainer (Undertone0809/rudder, 292 stars), Release Engineering (majiayu000/spellbook, 286 stars), Cline Desktop App Release (cline/cline, 70k stars) and EverOS Release Workflow (EverMind-AI/EverOS, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Orchestrator?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.