Coordinate multi-phase OpenAPI toolkit release preparation across agents.
npx skills add https://github.com/erraggy/oastools --skill prepare-release-erraggy
Please help me install this Agent Skill. Skill: prepare-release Source: https://github.com/erraggy/oastools/tree/main/.claude/skills/prepare-release Command: npx skills add https://github.com/erraggy/oastools --skill prepare-release-erraggy
Coordinates a multi-phase release preparation workflow by orchestrating background agents, scripts, and release-note enhancements to ensure a thorough, repeatable process.
Invoke /prepare-release <version> to start the automated release preparation workflow.
High-intent search queries and answers about installing and using this skill.
Automated release preparation is coordinated by orchestrating background agents across DevOps, Architect, Maintainer, and Developer roles to validate and prepare a new release. It enforces centralized execution through the prepare-release.sh script to ensure a repeatable process.
You can infer a release version from conventional commits by omitting the version parameter when invoking the release preparation workflow. The system automatically analyzes the commit history to determine the appropriate version number without requiring manual input.
The best way to orchestrate a multi-phase release workflow is to use a centralized script that coordinates background tasks and enhances release notes. This approach manages phase orchestration across various roles and creates a dedicated release-prep branch for CI traceability.
A release-prep branch is automatically created as chore/<version>-release-prep during the release preparation workflow. This dedicated branch supports CI workflows and ensures traceability throughout the automated release process.
Release notes formatting is enhanced automatically during pre-release orchestration. The system processes and improves release notes stored in the .release directory, applying formatting enhancements as part of the centralized workflow execution.
You do not need to provide a version number to start the release preparation workflow. When a version is omitted, the system automatically infers the correct release version by analyzing conventional commits in the repository.
LanceRabbitGenerate conventional commit messages from staged and unstaged git diffs.
erraggyValidate a version argument and publish a GitHub release from the main branch.
Hoang604Aggregate phase summaries from ROADMAP.md into a conventional commit message.
BagelHoleAutomate version bumps and changelog generation from Conventional Commits.
