skills.rest
CyanAutomation
CyanAutomationCOMMUNITY
Explore all skills by this author →
GitHub

release-operator

Coordinate tag-driven release automation across GitHub Actions and container image workflows.

1|Updated Jan 14, 2026
Search Tags:#automation#git#versioning#rollback#release#github-actions#ci-cd
One-click install
npx skills add https://github.com/CyanAutomation/motioninocean --skill release-operator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-operator
Source: https://github.com/CyanAutomation/motioninocean/tree/main/.github/skills/release-operator
Command: npx skills add https://github.com/CyanAutomation/motioninocean --skill release-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates tag-driven release automation, including preflight checks, release execution, workflow verification, and rollback handling to ensure reliable software releases.

Core Features & Use Cases

  • Preflight checks and validation of version bumps
  • Release execution, tag creation, and GHCR publishing verification
  • Rollback handling and failure recovery guidance for failed releases

Quick Start

Run the release-operator to coordinate a new semantic version release and verify the release workflow across CI.

Frequently Asked Questions about release-operator

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

FAQPage Schema
How do I automate semantic version bumps and git tag releases in GitHub Actions?▼

Tag-driven release automation orchestrates semantic version bumps by validating version readiness, creating git tags, updating VERSION and CHANGELOG.md, and verifying GitHub Actions workflows.

What is the best way to verify a container image publishing workflow after a release?▼

Container image workflow verification checks the GitHub Actions status and GHCR publishing results after release execution, ensuring the published image matches the newly created semantic version tag.

How do I rollback a failed GitHub Actions release and recover the previous version?▼

Rollback handling reverts the semantic version bump by updating VERSION, modifying git tags, and restoring CHANGELOG.md, providing failure recovery guidance for failed release workflows.

What preflight checks are needed before creating a semantic version tag for a CI pipeline?▼

Preflight checks validate the semantic version bump, confirm CHANGELOG.md readiness, and verify GitHub Actions permissions before executing the tag-driven release.

Do I need GitHub Actions permissions to update VERSION and CHANGELOG.md for release automation?▼

Yes, tag-driven release automation requires explicit GitHub Actions permissions to update VERSION, modify CHANGELOG.md, and push git tags via the provided scripts.

Can I coordinate a release across GitHub Actions and container image workflows without manual intervention?▼

Release execution coordinates tag creation and publishing verification across GitHub Actions and container image workflows, automating the entire process from version bump to post-release checks.

Related Skills

Explore More Software Engineering Skills→
rickylabsrickylabs

netscript-release

Automate NetScript release cuts and GitHub publishing with Deno and GitHub Actions.

Community
Advanced
rudironsonirudironsoni

dotnet-gha-publish

Automate .NET artifact publishing in GitHub Actions workflows.

Community
Advanced
EndstoneMCEndstoneMC
715

release

Automate Endstone Minecraft Bedrock server releases with versioning, CHANGELOG updates, and CI/CD triggers.

Official
Advanced
figuedmundofiguedmundo

changelog-automation

Automate changelog generation and release management with Conventional Commits.

Community
Advanced