release

Automate Yuzu release management from preflight to publish and verification.

15|7|Updated Feb 28, 2026

Search Tags:#git #workflow #release #orchestration #cosign #gh-actions

Ready to run

npx skills add https://github.com/Tr3kkR/Yuzu --skill release-tr3kkr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Tr3kkR/Yuzu/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Tr3kkR/Yuzu --skill release-tr3kkr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cut through the manual labor of releasing software by orchestrating every step from preflight to verification, ensuring consistency and auditable releases.

Core Features & Use Cases

End-to-end release orchestration: preflight checks, version pin validation, tag pushing, CI workflow monitoring, artifact verification, and release notes generation.
Multi-destination publishing: automatic GitHub Releases artifacts and GHCR images with integrity checks and optional notarization/signing workflows.
Failure handling and recovery: deterministic phase flow with built-in troubleshooting guidance and resume/rollback options.
Compose Wizard packaging: optional bundling of the compose wizard assets into release artifacts.

Quick Start

Invoke the release flow by issuing /release vX.Y.Z to start an end-to-end release pipeline.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate a Git release workflow end-to-end with GitHub Actions?▼

The release process handles failure recovery through a deterministic phase flow with built-in troubleshooting guidance. It provides explicit resume and rollback options to help you navigate and correct CI workflow failures safely.

How does cosign verification work for GitHub Release artifacts?▼

Cosign verification for GitHub Release artifacts works by applying integrity checks and optional notarization or signing workflows during multi-destination publishing. This ensures the authenticity and tamper-proof integrity of released assets.

What is the best way to cut a new version tag vX.Y.Z and validate version pins?▼

The best way to cut a new version tag vX.Y.Z is to trigger an automated pipeline that validates version pins, pushes the tag, and monitors CI workflows. This orchestrates the entire process deterministically from preflight to publish.

Do I need cosign and SHA256 verification to publish GHCR images?▼

Yes, you need cosign and SHA256 verification to publish GHCR images if you require integrity checks and optional notarization. These are required components of the release workflow to verify asset availability and security.

What are the limitations when troubleshooting CI workflow failures during a release?▼

Troubleshooting CI workflow failures is limited to the deterministic phase flow's built-in guidance and resume or rollback options. It cannot bypass external GitHub Actions infrastructure failures or invalid Git repository states.