release-orchestrator

Automates semantic version bumping, release branch management, and git tag creation via Python scripts.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill release-orchestrator-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-orchestrator
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/release-orchestrator
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill release-orchestrator-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a software release manually—bumping versions across manifests, updating changelogs, running pre-release tests, and creating branches and tags—is error-prone and easy to get wrong. This Skill orchestrates the entire release workflow with deterministic Python scripts and strict quality gates. ## Core Features & Use Cases - Semantic Version Bumping: Determines the bump tier (MINOR by default, resetting PATCH to 0) and updates version manifests, changelogs, and release notes consistently. - Mandatory Pre-Release Quality Gates: Runs the local CI/CD test runner and validates that all unit tests, AST checks, and quality gates pass before any release proceeds. - Branch and Tag Automation: Creates release branches and git tags, then enforces a single atomic commit and push of all release artifacts to origin. - Use Case: When preparing a new release of the jpg2pdf CLI, invoke this Skill to verify tests pass, bump the version across all packages, generate release notes, tag the release, and push everything to the remote repository in one coordinated flow. ## Quick Start Run the release orchestrator to bump the minor version, verify all tests pass, and create and push the release branch and tag.

Frequently Asked Questions about release-orchestrator

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

FAQPage Schema
How do I automate semantic version bumping for a release?

Use the release orchestrator script, which determines the bump tier (MINOR by default, resetting PATCH to 0) and coordinates version updates across packages, changelogs, and git branches and tags in a single workflow.

How to run pre-release tests before creating a git tag?

Execute the local CI/CD runner with the --run-tests flag before tagging. The workflow requires all unit test suites, AST checks, and quality gates to pass with exit code 0, with a --skip-tests option reserved for emergency runs.

Can the release workflow commit files individually?

No. The workflow explicitly bans per-file commits. All modified files must be accumulated and committed together in a single grouped atomic commit at the final step before pushing the release branch, tag, and main branch to origin.

What happens if the git working tree is not clean before a release?

The release orchestration verifies git clean status before execution. A dirty working tree blocks the release, ensuring version bumps and tags are created from a consistent, committed state.

How does the release process validate test coverage for changed files?

It cross-references a record of recently modified files against a test inventory manifest to confirm that all test suites covering those files pass completely before the release proceeds.