release

Orchestrate production releases by discovering deploy commands and executing preflight, merge, tag, deploy, and audit steps.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill release-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/release
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill release-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cutting a production release end-to-end requires coordinating preflight checks, merging integration into main, tagging the release commit, deploying, pushing the tag, and recording AUDIT updates. This skill reads the project's CLAUDE.md / DEPLOY.md / manifests to discover the actual deploy command and enforces the consent-based release flow with hard blockers for auth, failed tests, dirty trees, and missing deploy commands.

Core Features & Use Cases

  • End-to-end release orchestration: preflight, merge, tag, deploy, push tag, and audit/record updates.
  • Deploy command discovery: reads CLAUDE.md, DEPLOY.md and manifests to locate the correct production commands without hardcoding.
  • Safety and compliance: stops on hard blockers and surfaces detailed failure information for auditability.

Quick Start

Invoke the release command to initiate the end-to-end release workflow for the current project.

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 production release and deployment?

Automating an end-to-end production release involves orchestrating preflight checks, merging code, tagging commits, deploying, and recording audit trails. This skill discovers deploy commands from project manifests to execute the complete workflow safely.

What are the prerequisites for automating deployment with project manifests?

Automating deployment requires existing CLAUDE.md, DEPLOY.md, and manifest files in your repository. The release workflow reads these documents to discover the correct production commands and validate the project environment before executing.

How do deployment blockers and consent checks work during a release?

Deployment blockers and consent checks work by halting the release workflow when critical issues are detected. The system stops on failed tests, dirty git trees, missing deploy commands, or authentication problems to ensure production safety and auditability.

How do I create annotated git tags and audit trails for versioning?

Creating annotated git tags and audit trails happens automatically during the release orchestration. After merging integration branches into main, the system creates annotated tags for the release commit, pushes them, and records detailed AUDIT updates for compliance tracking.

Why does my release workflow stop before deploying to production?

Your release workflow stops before deploying to production because hard blockers were triggered during preflight validation. The system enforces consent-based safety by halting on failed tests, dirty trees, missing deploy commands, or authentication failures, surfacing detailed failure information for review.