Agent skill

Release Changelog Harness

by Arenukvern in Arenukvern/mcp_flutter

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable.

MITAuto-check passedDevelopment

Install Release Changelog Harness

skills CLI
$ npx skills add Arenukvern/mcp_flutter --skill release-changelog-harness -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Arenukvern/mcp_flutter release-changelog-harness --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-changelog-harness .claude/skills/release-changelog-harness && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-changelog-harness
GitHub stars
387
Token cost
~2.6k tokens
SKILL.md length
1,017 words
Files
5 (incl. references)
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable.

  • Works in 6 steps: Classify the repo → Choose generator (ADR if non-obvious) → Wire harness surfaces → …
  • Shipping MCP/CLI without clone
  • SKILL.md covers Mixture of experts — critique…, Release legibility contract…, Ecosystem router (default… and When to use this skill, plus 5 more sections
  • Calls pnpm, npx and git; needs GITHUB_TOKEN

What it does

Release Changelog Harness is an agent skill from Arenukvern/mcp_flutter. Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/binary-release-contract.md`, `references/ecosystem-tooling.md` and `references/mixture-of-experts.md`).

It sits in Development, covering Changelog and release notes. It works with Model Context Protocol, GitHub and Git. The repository describes itself as: MCP Toolkit for Flutter AI Agent Driven Development (MCP/CLI + custom client side tools) - via closed feedback loop (visual & semantic snapshot) and high client side… The licence is MIT.

When your agent uses it

  • Shipping MCP/CLI without clone
  • Meta repos that only ship skills via npx skills—not domain app tutorials

Example prompts

  • “Use the release-changelog-harness skill to choose ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary…”
  • “/release-changelog-harness”

Requirements

  • Node.js
  • A credential in GITHUB_TOKEN

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Classify the repo
  2. Choose generator (ADR if non-obvious)
  3. Wire harness surfaces
  4. Minimal Changesets shape (JS monorepos and private packages)
  5. Choose distribution surface
  6. Verify legibility

What it can do on your machine

Read from SKILL.md and the folder at commit 62f3ee1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • npx
    • git
    • changeset
    • dart

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • melos.invertase.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Changelog Harness loads about 2.6k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 1,017 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Arenukvern/mcp_flutter at commit 62f3ee1, republished under its MIT licence (© Arenukvern). 1,017 words, ~2,596 tokens.

Download SKILL.mdSave it as .claude/skills/release-changelog-harness/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
release-changelog-harness
description
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.
license
MIT
type
governance
metadata.author
skill-steward
metadata.version
1.2.0
metadata.category
harness
paths
CHANGELOG.md, .changeset/**, package.json, pnpm-workspace.yaml, pubspec.yaml, Cargo.toml, .github/workflows/*release*, .github/workflows/*publish*

Release & changelog harness

Make releases understandable: every version bump has structured intent that agents and humans can read in git—not only in a maintainer’s head or a GitHub Releases textarea.

This skill is meta harness culture (which tool, which gates, which docs). It is not a full tutorial for every package manager.

Mixture of experts — critique your idea

Expert lensVerdict on “use JS Changesets everywhere”
JS monorepo maintainerStrong default: .changeset/*.md + changeset version beats hand-editing five package.json files.
Dart / Flutter publisherWeak fit as-is: pub uses tags + CHANGELOG.md; monorepos often use Melos version / changelog, not npm Changesets.
Rust / Go shipperUse release-plz, cargo-release, or git-cliff—forcing Changesets adds alien workflow.
Agent operatorWins when notes live as small structured files in git agents can read and PR—not prose-only in Slack.
Multi-repo steward (~/mcp)One legibility contract across siblings; different generators per ecosystem is fine.
Skill Steward charterTeach when + gate + doc placement; link to upstream docs; do not paste 200-line configs into SKILL.md.

Improved framing (use this):

Adopt the release legibility contract first; pick the ecosystem-native generator second (Changesets is one excellent generator for JS workspaces, not the universal hammer).

See mixture-of-experts.md for extended debate and anti-patterns.

Release legibility contract (normative)

Before picking a tool, agree the repo obeys:

  1. Notes in git — Changelog or changeset files are versioned; not release-notes-only in a web UI.
  2. Structured contributor input — Contributors add intent in a fixed shape (e.g. .changeset/foo.md, conventional commit scope, or ADR note)—not “bump version when you remember.”
  3. Mechanical publish path — One documented command sequence in DX_FAQ; CI is the source of truth for “can ship.”
  4. Agent-readable output — Post-release, CHANGELOG.md (or per-package changelogs) reflects what shipped; agents can answer “what changed in vX?”
  5. Why is recorded — Non-obvious toolchain choice → short ADR or DESIGN_FAQ Q&A.
  6. Install trust matches release truth — The latest GitHub Release, release assets, checksums, package versions, and install docs must agree; stale pinned install examples are release drift.

Ecosystem router (default patterns)

Signal in repoDefault toolingNotes
pnpm-workspace.yaml / npm workspaces@changesets/cliIndustry standard for JS monorepos; pair with GitHub Action.
Single Node package, high release cadencerelease-please or Changesetsrelease-please = conventional commits → PR; Changesets = explicit human/agent intent files.
Dart monorepo (melos.yaml)Melos version + changelogAlign with pub publish order in DX_FAQ.
Single Dart packageCHANGELOG.md + git tag + dart pub publishKeep entries agent-editable markdown.
Rust workspacerelease-plz or cargo-release + git-cliffPrefer automation that opens version PRs.
Product harness w/ binariesrelease-please + tag CI + install.shDo not add a second version source; follow binary-release-contract.md
Meta + CLI binary (Skill Steward)Changesets + single Release workflow + install.shVersion PR updates git truth first; the release workflow tags, builds assets, creates/updates GitHub Release, and verifies latest/install trust per ADR 0014

Full matrix: ecosystem-tooling.md. Binary/install: binary-release-contract.md.

When to use this skill

  • “We should use Changesets like the JS community”
  • Release process is unclear, versions drift, or agents can’t tell what shipped
  • Adding release CI, versioning policy, or monorepo publish workflow
  • Auditing whether changelog tooling matches repo archetype (repo-quality-system-lifecycle)

Workflow

1. Classify the repo

Use repo-quality-system-lifecycle archetypes (app, library, CLI/tool, plugin, harness, meta/governance). Meta and harness repos need legibility; app repos need legibility and runtime compatibility notes.

2. Choose generator (ADR if non-obvious)
QuestionIf yes →
Multiple publishable JS packages?Changesets (default)
Single package, commit-msg driven releases?release-please
Maintainer writes explicit release notes per PR?Changesets
Pub or Cargo primary?Ecosystem table above—not Changesets

Record choice in docs/decisions/NNNN-release-changelog-tooling.md when more than one option is reasonable.

3. Wire harness surfaces
SurfaceAction
DX_FAQMemory-palace block: add changeset, version, publish, verify tag
CIBlock publish/tag if changesets/changelog policy violated; for binaries, use one release owner or an explicit workflow_run/PAT handoff
AGENTS.mdOne row in doc router—no full Changesets essay
CONTRIBUTING“Every user-facing PR adds a changeset or CHANGELOG entry”
Show full SKILL.md (389 more words)Show less
4. Minimal Changesets shape (JS monorepos and private packages)

Contributor adds:

markdown
---
"package-name": patch
---

Short imperative summary agents can quote in release notes.
Private Packages and Public Tags

By default, Changesets ignores packages marked with "private": true in package.json. To allow version bumps for a private root package or private workspace modules, update .changeset/config.json to include:

json
  "privatePackages": {
    "version": true,
    "tag": false
  }

Use "tag": false when a custom release script owns the public vX.Y.Z tag. Use "tag": true only when Changesets itself should create package-scoped tags.

Maintainer flow:

bash
pnpm changeset          # or npx @changesets/cli
pnpm changeset version
pnpm install            # if lockfile must update
git commit -am "chore: version packages"

Publish: project-specific (changeset publish, GitHub Action, or npm provenance)—document exact commands in DX_FAQ, not here.

For automated Changesets releases, prefer:

text
merge feature PR with changeset
→ CI opens/updates Version PR
→ merge Version PR
→ same Release workflow creates vX.Y.Z, builds artifacts, creates/updates GitHub Release, verifies latest release state

If the tag is pushed with GITHUB_TOKEN, do not depend on a separate on: push: tags workflow to build assets; GitHub suppresses recursive workflow triggers for that token.

5. Choose distribution surface
Ship unitPattern
Executable MCP/CLIGitHub Release binaries + checksums + install.sh — binary-release-contract.md
Skills onlynpx skills add owner/repo — no repo tarball for consumers
Librariespub.dev / npm / crates.io per ecosystem table

Skill Steward: skills via npx skills; steward_cli precompiled AOT binaries via GitHub Releases & install.sh (ADR 0014).

6. Verify legibility
  • Agent can read “what’s unreleased” from git without GitHub API
  • CI fails when a version bump lacks notes
  • DX_FAQ lists commands copy-paste ready
  • No duplicate version sources (e.g. hand bump + bot bump)
  • If binaries: tag assets match version SSOT; latest GitHub Release points to the package version; install.sh defaults to latest and pinned examples use placeholders or generated checks

Anti-patterns

Anti-patternWhy it hurts
Changesets in a Rust-only repoWrong culture; contributors ignore it
Changelog only on GitHub ReleasesAgents in repo context miss it
1,000-line release doc in AGENTS.mdCrowds task context; belongs in DX_FAQ / ADR
Skipping changesets “because AI will write CHANGELOG at release”Non-deterministic; no PR-time review
Version bumps without consumer-facing sentenceUsers and agents can’t assess upgrade risk
Binary Releases without changelog in gitUsers see version; agents miss intent
Separate tag-triggered binary workflow after a GITHUB_TOKEN tag pushGitHub suppresses recursive workflow triggers; latest release/assets can silently lag
Static pinned install examples with real old versionsREADME/DX says one thing while GitHub Releases/install.sh say another
git clone as end-user install for a server productUse install.sh + Release assets (binary release pattern)
SkillUse for
repo-quality-system-lifecycleRepo archetype, mechanical gates, evidence path
mcp-harness-repo-maintainerTyped actions, probes, benchmarks, CLI/MCP parity
repository-governance-lifecycleADRs, DESIGN_FAQ/DX_FAQ updates, and plan hygiene
skill-source-citationsDurable release-tooling sources

Install

bash
npx skills add arenukvern/skill_steward --skill release-changelog-harness

Sources

references/sources.md

© Arenukvern, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in .agents/skills/release-changelog-harness of Arenukvern/mcp_flutter.

  • SKILL.md
  • references/binary-release-contract.md
  • references/ecosystem-tooling.md
  • references/mixture-of-experts.md
  • references/sources.md

Open the folder on GitHubat commit 62f3ee1

Compare with similar skills

Release Changelog Harness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Changelog Harness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Changelog Harness this skillArenukvern/mcp_flutter387—~2.6kAutomated safety check: PassMIT
Git Releasewesammustafa/opencode-primer399—~409Automated safety check: PassMIT
Release Crater3bl-org/r3bl-open-core485—~2.4kAutomated safety check: PassApache-2.0
Rea Changelog Updatemorluto/rea80k—~1.9kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0

Similar skills

  • Git Release

    wesammustafa/opencode-primer

    Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable gh release create command.

    399 GitHub stars~409 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Release Crate

    r3bl-org/r3bl-open-core

    Publish a crate release to crates.io with changelog, standalone release notes, git tag, and GitHub release.

    485 GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

    80k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from Arenukvern/mcp_flutter

All 23 skills in this repo
  • Harness Engineering Lifecycle

    Arenukvern/mcp_flutter

    Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.

    387 GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed
  • Mixture Of Experts

    Arenukvern/mcp_flutter

    Run a Mixture of Experts (MoE) audit on any topic, plan, codebase, evidence archive, or process.

    387 GitHub stars~2.3k tokensUpdated 8 days ago
    Auto-check passed
  • Multi Agent Handoff

    Arenukvern/mcp_flutter

    Plan and document handoffs, parent lane contracts, and parallel batch contracts between specialized AI agents (foreman, workers, reviewers).

    387 GitHub stars~2.7k tokensUpdated 8 days ago
    Auto-check passed
  • Plugin Marketplace Setup

    Arenukvern/mcp_flutter

    Designs public or private Agent Skill and plugin marketplaces for Cursor, Claude Code, Codex, Zed, Open Plugin, and npx skills—manifest layout, install matrix, and Skill Steward vs product boundaries.

    387 GitHub stars~2.9k tokensUpdated 8 days ago
    Auto-check passed
  • Repository Governance Lifecycle

    Arenukvern/mcp_flutter

    Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks.

    387 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed
  • Skill Authoring Lifecycle

    Arenukvern/mcp_flutter

    Scaffold and formally review a new Agent Skill in this marketplace repo.

    387 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed

Categories

Questions about Release Changelog Harness

What does Release Changelog Harness do?

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Release Changelog Harness is an agent skill from Arenukvern/mcp_flutter.sh) when the product is an executable.

When should I use Release Changelog Harness?

Release Changelog Harness fits situations like: shipping MCP/CLI without clone; meta repos that only ship skills via npx skills—not domain app tutorials.

How do I install Release Changelog Harness in Claude Code?

Run `npx skills add Arenukvern/mcp_flutter --skill release-changelog-harness -a claude-code`. Or copy the skill folder (.agents/skills/release-changelog-harness in Arenukvern/mcp_flutter) into .claude/skills/release-changelog-harness in your project. Claude Code loads it when a task matches its description.

How do I install Release Changelog Harness in Codex?

Run `npx skills add Arenukvern/mcp_flutter --skill release-changelog-harness -a codex`. Or copy the skill folder (.agents/skills/release-changelog-harness in Arenukvern/mcp_flutter) into .agents/skills/release-changelog-harness in your project. Codex loads it when a task matches its description.

Can I use Release Changelog Harness in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Arenukvern/mcp_flutter --skill release-changelog-harness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-changelog-harness, .gemini/skills/release-changelog-harness, .github/skills/release-changelog-harness and .opencode/skills/release-changelog-harness in your project.

What does Release Changelog Harness need to run?

Going by SKILL.md and its folder, Release Changelog Harness needs the command-line tools its instructions call (pnpm, npx, git, changeset and dart) and credentials named GITHUB_TOKEN. Our summary lists: Node.js; A credential in GITHUB_TOKEN.

Does Release Changelog Harness access the network?

SKILL.md names 2 domains. As links in the text: github.com and melos.invertase.dev. This is read from the text; nothing was executed.

Is Release Changelog Harness safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Changelog Harness use?

Release Changelog Harness is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Changelog Harness use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.

What are the alternatives to Release Changelog Harness?

Skills that share tags, products or a category with Release Changelog Harness: Git Release (wesammustafa/opencode-primer, 399 stars), Release Crate (r3bl-org/r3bl-open-core, 485 stars), Rea Changelog Update (morluto/rea, 80k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Changelog Harness?

Arenukvern (a GitHub user) maintains it in Arenukvern/mcp_flutter, which has 387 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 3, 2026.

Source: Arenukvern/mcp_flutter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.