auto-release

Inspect commits since the last tag and trigger the release pipeline.

3|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/cloga/optimus-code --skill auto-release-cloga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-release
Source: https://github.com/cloga/optimus-code/tree/main/.optimus/skills/auto-release
Command: npx skills add https://github.com/cloga/optimus-code --skill auto-release-cloga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release decision gate and execution pipeline by inspecting commits since the last tag and triggering a controlled release through the release-process skill.

Core Features & Use Cases

  • Reads release policy from .optimus/config/release-policy.json and applies sane defaults when missing.
  • Enforces cooldowns, computes the required semver bump from Conventional Commits, and guards against auto-release when not permitted.
  • Orchestrates the full release flow: extra gates, test suite, build, tagging, push, and post-release verification via the release-process skill.

Quick Start

Configure the release policy under .optimus/config/release-policy.json and ensure the release-gate cron is active to start automated releases.

Frequently Asked Questions about auto-release

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

FAQPage Schema
How do I automate scheduled software releases based on conventional commits?

Automated releases inspect commits since the last tag, compute the required semver bump from Conventional Commits, and trigger the release pipeline via a cron gate. This enforces cooldowns and extra gates before tagging and pushing.

How does an automated release gate handle cooldowns and version bumps?

The release gate reads .optimus/config/release-policy.json to enforce cooldowns, calculate the maximum allowed automatic semver bump, and block auto-release when the commit history or policy constraints do not permit it.

What is the best way to trigger a CI CD release pipeline only when tests pass?

Orchestrate the release flow by running test suites and extra gates first, then triggering the build, tagging, and push phases only if all checks pass, followed by post-release verification across repositories.

Do I need a specific configuration file to enforce an automated release policy?

Yes, you need to configure the release policy under .optimus/config/release-policy.json. The system applies sane defaults when the file is missing, but explicit configuration is required to define max auto-bump limits and cooldowns.

Can I coordinate automated releases across multiple repositories with safety guards?

Yes, the release coordination process applies safety guards across repositories, updating session history and allowing optional human input when needed to ensure safe multi-repository release execution.