release-cch

Automate CCH release workflows from version management to GitHub publishing.

46|8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/SpillwaveSolutions/code_agent_context_hooks --skill release-cch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-cch
Source: https://github.com/SpillwaveSolutions/code_agent_context_hooks/tree/main/.opencode/skill/release-cch
Command: npx skills add https://github.com/SpillwaveSolutions/code_agent_context_hooks --skill release-cch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, cargo, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the end-to-end release workflow for Claude Context Hooks (CCH), reducing manual steps from version bumps to GitHub release publishing.

Core Features & Use Cases

  • Version management: reads the current version from Cargo.toml, proposes a new semantic version, and documents changes.
  • Release orchestration: creates a dedicated release branch, runs preflight checks, generates changelog, and coordinates PR creation.
  • Tagging & publishing: merges the release PR, creates a Git tag, and publishes release assets on GitHub, including platform builds and checksums.
  • Hotfix support: provides a streamlined workflow to patch an existing release with minimal changes.
  • Use Case: When you need to release a new version of Claude Context Hooks across Linux, macOS, and Windows, with automated changelog and release notices.

Quick Start

Start the release by reading the current version and following the standard workflow:

  • Read current version: .opencode/skill/release-cch/scripts/read-version.sh
  • Bump version in Cargo.toml and commit
  • Run preflight checks: .opencode/skill/release-cch/scripts/preflight-check.sh
  • Generate changelog: .opencode/skill/release-cch/scripts/generate-changelog.sh ${VERSION}
  • Create and merge a release PR, then tag and push: git tag v${VERSION}; git push origin v${VERSION}
  • Verify the release: .opencode/skill/release-cch/scripts/verify-release.sh

Frequently Asked Questions about release-cch

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

FAQPage Schema
How do I automate semantic versioning and GitHub release publishing for Rust projects?

To automate semantic versioning and GitHub release publishing for Rust projects, you read the current version from Cargo.toml, generate a changelog, create a release branch, and push Git tags to trigger a GitHub Actions workflow that builds and publishes release assets.

What is the standard workflow for generating a changelog and tagging a release across Linux, macOS, and Windows?

The standard workflow for generating a changelog and tagging a cross-platform release involves running preflight checks, executing a changelog generation script, merging a dedicated release PR, and pushing a Git tag to trigger cross-platform GitHub Actions builds.

Can I use GitHub Actions and Cargo to orchestrate a hotfix release for an existing version?

Yes, you can use GitHub Actions and Cargo to orchestrate a hotfix release by following a streamlined workflow that patches an existing release branch with minimal changes, rebuilds the binaries, and pushes the corrected tag to GitHub.

Do I need git and gh installed to automate version bumps and PR creation for my releases?

Yes, you need git and gh installed to automate version bumps and PR creation, as the release automation relies on these dependencies to read versions from Cargo.toml, commit changes, create release branches, and manage pull requests via GitHub Actions.

How does this approach handle release orchestration compared to manual version management in Cargo.toml?

This approach handles release orchestration by automating the manual version management steps in Cargo.toml, coordinating changelog generation, preflight checks, and GitHub Actions monitoring, which eliminates the friction and potential errors of manual version bumps and tagging.