Automate the full release pipeline — conventional-commit semver calculation, CHANGELOG update, git tag creation, and optional GitHub release — with a durable release-summary.md artifact.
From workflow-orchestrationnpx claudepluginhub mikecubed/agent-orchestration --plugin workflow-orchestrationThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Automates the full release pipeline for plugin and software projects. The skill walks through each stage of the pipeline in order:
--create-release is passed and
the gh CLI plus a valid GitHub token are available, creates a GitHub release
using the new CHANGELOG section as the release body.Every invocation produces a durable release-summary.md artifact documenting
the version source, commits included, tag status, GitHub release status, and any
skipped steps with reasons.
The skill supports both a calculated-version path (derived from conventional
commits) and an explicit --version override path that bypasses semver
calculation entirely.
Persistent team, squad, or fleet-style long-lived orchestration is out of scope for this skill.
--version override path.| Input | Required | Notes |
|---|---|---|
| Project root path | Yes | Must be the root of the git repository. |
--version override | No | Skips semver calculation entirely; the provided version is used as-is. |
--create-release flag | No | Triggers GitHub release creation if gh CLI + token are available. |
| Release notes override text | No | Custom body text for the GitHub release (replaces CHANGELOG section). |
| Git tag history availability | Yes | Shallow clones are a stop condition — full clone required. |
GitHub token + gh CLI | Only for --create-release | Graceful skip if absent; local steps still complete. |
Gather factual context: confirm git history depth, last tag, conventional commit log, and working tree cleanliness before proceeding.
--version override is supplied:
feat: → minor bumpfix:, chore:, docs: → patch bumpBREAKING CHANGE: footer or feat!: / fix!: → major bump--version → skip calculation entirely; document override in
release summary.release-summary.md, and exit without modifying CHANGELOG.md or creating
a release.CHANGELOG.md using the project's existing dated
[version] - YYYY-MM-DD format with commits grouped by type.--create-release AND gh CLI
available AND GitHub token present: create the release using the new
CHANGELOG.md section as the release body.--create-release but gh CLI
unavailable OR no GitHub token: complete all local steps, document
"GitHub release skipped: gh CLI unavailable / no token" in
release-summary.md, do not fail.release-summary.md artifact recording:
release-summary.md, exit without modifying
CHANGELOG.md or creating a release.--create-release with no gh CLI or no GitHub
token → complete local steps, document skip, do not fail the skill.release-summary.md recording completed and skipped steps before halting.Scenario: A plugin repository is currently at v0.9.0. Two conventional
commits have landed since that tag:
feat: add contract-generator
fix: resolve OpenAPI schema edge case
Invocation:
/workflow-orchestration:release-orchestration
Result:
The skill reads the two commits and determines that the feat: commit
triggers a minor bump: v0.9.0 → v0.10.0.
It verifies that the tag v0.10.0 does not already exist.
CHANGELOG.md is updated with a new section:
## [0.10.0] - 2025-07-17
### Features
- add contract-generator
### Bug Fixes
- resolve OpenAPI schema edge case
Git tag v0.10.0 is created.
release-summary.md is emitted documenting:
0.10.0feat:)feat: add contract-generator, fix: resolve OpenAPI schema edge casev0.10.0--create-release flag)Note: To produce
v1.0.0fromv0.9.0, use afeat!:commit (breaking change) or the--version 1.0.0override.