skills.rest
hieubui2409
hieubui2409COMMUNITY
Explore all skills by this author →
GitHub

cleanmatic:release

Package versioned .claude/ artifacts into a deterministic tarball with SHA256 manifest.

17|8|Updated May 28, 2026
Search Tags:#changelog#versioning#packaging#release#manifest#deterministic#tarball
One-click install
npx skills add https://github.com/hieubui2409/product-spec --skill cleanmatic-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cleanmatic:release
Source: https://github.com/hieubui2409/product-spec/tree/main/.claude/skills/release
Command: npx skills add https://github.com/hieubui2409/product-spec --skill cleanmatic-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The release process for distributed .claude/ bundles is manual and error-prone; this skill automates packaging and coordinating versioned bundles with a deterministic tarball and a changelog lifecycle.

Core Features & Use Cases

  • Build a versioned tarball from a curated subset of .claude/ (skills, agents, hooks, rules) plus optional top-level files.
  • Manage the root CHANGELOG Keep-a-Changelog lifecycle by locking Unreleased into a version and bumping manifest.
  • Produce platform installers (install.sh, install.ps1) and per-file SHA256 manifest for reproducible releases.

Quick Start

Ask me to pack a versioned, deterministic bundle from the repository and lock the root CHANGELOG for the release.

Frequently Asked Questions about cleanmatic:release

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

FAQPage Schema
How do I package a deterministic release tarball from .claude artifacts?▼

To package a deterministic release tarball, the skill automates bundling a curated subset of .claude artifacts like skills, agents, hooks, and rules into a single versioned archive with a SHA256 sidecar for reproducible distribution.

How does Keep-a-Changelog versioning work when bundling a repository release?▼

Keep-a-Changelog versioning works by locking the Unreleased section in the root CHANGELOG into a specific version and bumping the manifest, synchronizing changelog lifecycle with the release bundle generation.

Can I generate installers and SHA256 manifests for .claude release bundles?▼

Yes, you can generate platform installers and SHA256 manifests for release bundles. The process produces install.sh and install.ps1 scripts alongside per-file SHA256 checksums to ensure reproducible releases.

What is the best way to automate versioned manifest creation for release CI?▼

The best way to automate versioned manifest creation is using a release skill that validates inputs, renders embedded scripts, and writes the tarball, SHA256 sidecar, and versioned manifest ready for release CI pipelines.

Do I need top-level files included when packaging repository artifacts for release?▼

You do not strictly need top-level files, but the packaging process supports bundling optional top-level files alongside the curated subset of skills, agents, hooks, and rules within the .claude directory.

Why does my release tarball need a SHA256 sidecar file?▼

A release tarball needs a SHA256 sidecar file to guarantee deterministic and reproducible releases. It provides cryptographic checksums for verifying artifact integrity during distribution and installation.

Related Skills

Explore More Software Engineering Skills→
chen-001chen-001

gen-changelog

Generate changelog entries from branch differences and sync release notes.

Community
Advanced
quaid-appquaid-app
3

release-asset-contract

Align release assets and artifacts to a single authoritative manifest.

Official
Advanced
dhruvinrsonidhruvinrsoni

release-notes

Parse git history to generate changelogs and release notes.

Community
Advanced
EvolutionAPIEvolutionAPI
520

dev-release

Generate changelogs, bump semver versions, commit, and tag git releases.

Official
Intermediate