release

What it does and when to use it

Cut a harness-eval release - bump the version in the three manifest fields and the README version badge, update CHANGELOG (EN+KO), tag. Use only when the user asks to release.

How it works

1. Procedure
2. Summary

---
name: release
description: Cut a harness-eval release - bump the version in the three manifest fields and the README version badge, update CHANGELOG (EN+KO), tag. Use only when the user asks to release.
disable-model-invocation: true
---

# Release Skill

This repository is a monorepo: the marketplace manifest is at the root
(`.claude-plugin/marketplace.json`) and the plugin lives under
`plugins/harness-eval/`.

## Procedure

Follow `plugins/harness-eval/docs/runbooks/release.md` §1-6 - it is the single source for the command sequence: run `bash tests/harness-run-all.sh` from `plugins/harness-eval/` (it covers every suite), bump the three manifest fields and the README version badge (`version-X.Y.Z-green.svg`), move `[Unreleased]` into a dated `[X.Y.Z] - YYYY-MM-DD` section in both the English and 한국어 halves of CHANGELOG.md (leave an empty `[Unreleased]`), commit, then create the annotated tag on that commit.

Propose the version from the changes since the last tag (there may be no tag yet), using the runbook's SemVer rules (MAJOR = breaking plugin contract: script args, output schema, events), and show the CHANGELOG diff before committing. Do not push the branch or tag without the user's go-ahead.

## Summary

- Version bump (old → new)
- Key changes
- Next steps (push the branch and tag; verify the install per runbook §7)

Versions

Database snapshot: 13.11.2026 · package version e045ed35b8bf (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100ship-release
  Use when the user asks to release, ship, publish, cut or tag a version of a project ("release v0.2.0", "ship a patch", "bump and publish"). Bumps every version manifest, updates CHANGELOG and README badges, commits, lands it directly or through a pull request (pre-PR check,…
• 90bump
  This skill should be used when the user asks to "bump version", "bump new version", "release new version", "update version", "create a release", or any task involving incrementing the crux-hive plugin version, updating the changelog, and creating a release PR.
• 90release-tag
  Cut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally signed) Git tag, and pushing the release safely after pre-flight checks. Use when tagging a version, bumping the…
• 100version
  This skill should be used when the user wants to bump versions, create releases, or tag versions. Triggers include: "bump version", "bump the version", "version bump", "release version", "tag a release", "create release", "major/minor/patch bump", "update version", "new…
• 100ship
  Run a release end to end, autonomous by default: version bump everywhere, changelog, docs, landing page, tag, push, GitHub release, PyPI/npm. Use to ship, cut, or tag a release. Don't use for routine commits, pull requests, or marketplace publishing.
• 90qmai-release
  Release a stable QMAI version by updating version metadata and changelog, pushing main, then creating and pushing an annotated version tag. Use when asked to bump, publish, or tag a QMAI stable release; do not use for prerelease builds or ordinary PR delivery.