agentleFS
Sign inStart free
NeogenuityNeogenuity/harness-kit/.agents/skills/release/SKILL.md

release

Skill0 starsChanged 4 months agoMITView on GitHub

Cut a harness-kit release: run the quality gates, bump the plugin version, update the changelog, refresh this repo's own installed harness and manifest, and tag. Activates when asked to release, publish, cut, or tag a new version of harness-kit, or to prepare a version bump.

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read docs/standards/templates.md — especially version discipline.

    line 18
  2. Very specific:

    Add the CHANGELOG.md entry: user-facing changes first, mechanism changes with their migration note (does update mode replace the file, or …

    line 31
  3. Very specific:

    If plugins/harness-kit/skills/harness-kit/templates/scripts/ changed since the last release, roll the changes into this repo's own …

    line 37
  4. Very specific:

    Do not re-pin with init step 8's harness_generate_manifest — that producer emits no # tailored markers and drops retired tailored-only …

    line 47
  5. Very specific:

    Commit release: v<version>, tag v<version> (annotated), push with --follow-tags.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 186 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release

Ship a new plugin version. "Done" means: gates green, version bumped, changelog entry written, the root dogfood installation upgraded to match the templates being shipped, and an annotated tag pushed.

Prerequisites

  • Read docs/standards/templates.md — especially version discipline.
  • Working tree clean apart from the release changes; main up to date.

Steps

  1. bash scripts/harness/verify — all gates green before anything else.
  2. Decide the version (semver: mechanism behavior or template layout changes are at least minor while pre-1.0). plugins/harness-kit/VERSION is the single source of truth — set it there, and set the same value in both plugins/harness-kit/.claude-plugin/plugin.json and plugins/harness-kit/.codex-plugin/plugin.json. scripts/check-packaging.sh (the verify manifests gate) fails unless all three agree (see ADR 007).
  3. Add the CHANGELOG.md entry: user-facing changes first, mechanism changes with their migration note (does update mode replace the file, or diff it?).
  4. Sweep README.md and any status docs for version references that would go stale — README must not carry a hardcoded kit version (see Common Mistakes).

  5. If plugins/harness-kit/skills/harness-kit/templates/scripts/ changed since the last release, roll the changes into this repo's own installation (the kit's update mode: replace manifest-matching files in scripts/, diff tailored ones), then re-pin scripts/harness/.harness-manifest with the new version header and checksums:

    bash -c 'HARNESS_ALLOW_MECHANISM_EDITS=1 bash scripts/harness/bootstrap repin . <version>'

    Do not re-pin with init step 8's harness_generate_manifest — that producer emits no # tailored markers and drops retired tailored-only paths from the pin set, so on a repo with existing tailored pins the next update mode sees unmarked non-policy pins that match the tailored content and classifies them "replace" — silently clobbering the tailored copies with pristine templates (retired ones just fall out of integrity pinning). bootstrap repin preserves the markers, refuses missing arguments, and writes atomically; generate is the fresh-install producer, for trees with no tailored pins to preserve. This step is CI-enforced: scripts/harness/tests/test-template-sync.sh fails when a non-tailored installed file differs from its template.

  6. bash scripts/harness/verify again — the manifest gate must pass post-re-pin.
  7. Commit release: v<version>, tag v<version> (annotated), push with --follow-tags.

Verification

  • bash scripts/harness/verify passes on the release commit.
  • git show v<version> shows the tag on the release commit.
  • plugins/harness-kit/VERSION, both plugin.json versions, and the CHANGELOG heading all state the same version (check-packaging.sh enforces the version trio). The scripts/harness/.harness-manifest header matches only when step 5 ran — it records the last release that changed templates/scripts/, so it legitimately lags on a docs-only release (v0.13.0 shipped with the header at 0.12.0).
  • grep -nE '\bv?[0-9]+\.[0-9]+\.[0-9]+' README.md returns no kit-version claims that contradict plugins/harness-kit/VERSION (install-command examples and provider version stamps are fine).

Common Mistakes

  • Re-pinning the manifest before rolling template changes into scripts/ — the pin then blesses the stale copy and CI goes green on a lie.
  • Bumping only one version field — the version lives in plugins/harness-kit/VERSION and must be mirrored into both plugin.json files; the packaging gate fails on any mismatch.
  • Forgetting --follow-tags, so the marketplace serves the new version but the tag never reaches the remote.
  • Letting README go stale — a hardcoded v0.6.0 sat in README's Status section through two releases because no step owned sweeping it; README now points at plugins/harness-kit/VERSION instead of a literal version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free