x-release-harness_skill

Overview

This skill automates the Harness release workflow for the claude-code harness, letting you create CHANGELOG entries, bump VERSION, tag commits, and optionally publish a GitHub release in one flow. It streamlines verification, version determination, changelog updates (JP/EN), commits, tags, and pushes to reduce manual errors. Use it when you need a predictable, repeatable release process for harness versions.

How this skill works

The skill inspects the Git working tree, diff stats, and recent commits to summarize what changed and whether there are uncommitted files. It suggests a semantic version bump (patch/minor/major) based on changes, updates VERSION and plugin metadata, and inserts structured entries in both CHANGELOG.md and CHANGELOG_ja.md following the prescribed template. Finally it stages and commits changes, creates an annotated tag, pushes to origin, and can create a GitHub release with formatted release notes.

When to use it

• You need to release or bump the claude-code harness version (patch/minor/major).
• You want automated CHANGELOG entries in both English and Japanese for a harness release.
• You want to ensure commits, tags, and pushes follow a consistent release policy.
• You want a GitHub Release created with structured release notes.
• You need a quick, repeatable release flow to avoid manual mistakes.

Best practices

• Run the verification step first to catch uncommitted changes and unexpected diffs.
• Choose the semantic bump consciously: patch for fixes, minor for backward-compatible features, major for breaking changes.
• Focus changelog content on user-facing impact and use the Before/After table only for user-visible changes.
• Keep internal changes concise under an Internal section; avoid cluttering user-facing sections.
• Update README and plugin metadata when public-facing behavior or interfaces change.

Example use cases

• Create a patch release after fixing a user-facing bug and update CHANGELOG entries automatically.
• Perform a minor release to ship a new backward-compatible feature with proper Added and What’s Changed sections.
• Prepare a release candidate by running verification, generating structured commit lists for release notes, and tagging the release.
• Automate the full push and optional GitHub release creation to reduce release overhead for maintainers.