release

Name: release
Availability: InStock
Author: a7garden

Orchestrate CoHalo release workflows from changelog preparation to GitHub release.

Updated Mar 15, 2026

Search Tags:#changelog #publishing #github #release #docker #ci-cd

Ready to run

npx skills add https://github.com/a7garden/CoHalo --skill release-a7garden

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/a7garden/CoHalo/tree/main/skills/release
Command: npx skills add https://github.com/a7garden/CoHalo --skill release-a7garden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate the end-to-end CoHalo release process to eliminate manual steps and reduce risk when shipping features.

Core Features & Use Cases

End-to-end release orchestration from changelog drafting to GitHub release
Canary publishing, Docker smoke tests, and website announcement follow-ups
Preflight checks and a structured release model for patch/minor/major releases
Use Case: When leadership asks to ship a release, trigger a reproducible workflow that coordinates scripts and tagging.

Quick Start

Run a production release for the upcoming version (patch/minor/major) using the predefined release model.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate an end-to-end GitHub release with changelog preparation and Docker smoke tests?▼

Automate a GitHub release by orchestrating changelog drafting, prechecks, canary publishing, Docker smoke tests, and website announcements into a single reproducible workflow. This coordination eliminates manual scripting steps and reduces risk when shipping patch, minor, or major version updates.

What is the best way to coordinate a patch, minor, or major release workflow across multiple scripts?▼

Coordinate a release workflow by applying a structured release model that triggers predefined scripts for versioning, tagging, and publishing. This approach manages script coordination and release notes generation to ensure a production-ready deliverable without manual intervention.

Does this release orchestration model support canary publishing and Docker smoke tests?▼

Yes, release orchestration supports canary publishing and Docker smoke tests by coordinating them as intermediate steps. It applies prechecks before publishing canary versions and executes Docker smoke tests to validate stability before generating the final GitHub release.

What prechecks are needed before publishing a canary release to Docker?▼

Prechecks before publishing a canary release involve validating the structured release model and ensuring script coordination is ready. The workflow implements these preflight validations to eliminate manual steps and reduce risk before executing canary publishing and subsequent Docker smoke tests.

How do I generate release notes and tag a GitHub release after a successful smoke test?▼

Generate release notes and tag a GitHub release by completing the orchestration workflow after Docker smoke tests pass. The process automates release notes generation and applies version tagging to finalize the production-ready deliverable on GitHub.