claw-release_skill

Overview

This skill automates releases for Claw skills and the ClawSec catalog, guiding maintainers through version bumping, tagging, and post-release verification. It enforces semver, updates skill metadata, creates annotated tags, and integrates with CI to produce release artifacts. The tool is focused on repeatable, auditable releases for both public and internal skills.

How this skill works

The release script validates the new version string, ensures the git tag is unique, updates the skill.json version and the skill frontmatter, and replaces hardcoded versioned URLs. It commits changes, creates an annotated git tag, and pushes the tag to trigger CI. The pipeline then builds checksums, packages a .skill artifact, creates a GitHub Release, and triggers the website rebuild for public skills.

When to use it

• Preparing a routine bugfix, minor feature, or major breaking release
• Publishing a pre-release (alpha, beta, rc) for testing
• Ensuring version consistency across metadata and CI before pushing
• Automating repeatable releases to reduce human error
• Releasing internal-only utilities not shown in the public catalog

Best practices

• Decide version bump type before running the script: patch, minor, major, or pre-release
• Run pre-flight checks: git status, verify skill directory and current version
• Use the release script rather than manual tag edits to avoid metadata mismatches
• Commit or stash any local changes before releasing to keep history clean
• Verify CI run and release artifacts (checksums, package, release entry) after push

Example use cases

• Release a patch: fix a bug and run the script to produce <skill>-vX.Y.Z and a .skill package
• Publish a beta: create a 1.2.0-beta1 tag to share a preview with testers
• Undo a mistaken local release: roll back the last commit and delete the local tag before pushing
• Release an internal tool while keeping it out of the public catalog, but still available via direct release URL
• Trigger automated audits and checksum generation as part of the release CI for security verification