skills.rest
Arenukvern
ArenukvernCOMMUNITY
Explore all skills by this author →
Website𝕏@antmalofeevGitHub

release-changelog-harness

Selects ecosystem-native release and changelog tooling for versioning, CI, and binary distribution workflows.

2|Updated Aug 15, 2026
Search Tags:#changelog#versioning#monorepo#release automation#changesets#GitHub releases#ci cd
One-click install
npx skills add https://github.com/Arenukvern/shortly --skill release-changelog-harness-arenukvern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog-harness
Source: https://github.com/Arenukvern/shortly/tree/main/.agents/skills/release-changelog-harness
Command: npx skills add https://github.com/Arenukvern/shortly --skill release-changelog-harness-arenukvern

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Release processes often drift: versions get bumped without notes, changelogs live only in GitHub Releases, and agents cannot tell what shipped. This Skill establishes a release legibility contract and routes each repository to the correct ecosystem-native tooling instead of forcing one tool everywhere. ## Core Features & Use Cases - Release Legibility Contract: Enforces structured release notes in git, mechanical publish paths, CI gates, and agent-readable CHANGELOG output. - Ecosystem Router: Maps repo signals (pnpm workspaces, Melos, Cargo, single packages) to the right generator such as Changesets, release-please, release-plz, or git-cliff. - Binary Release Contract: Defines GitHub Release tarballs, checksums, and install.sh patterns for shipping CLI and MCP executables without git clone. - Use Case: A Dart monorepo maintainer wants Changesets because the JS community uses it; the Skill routes them to Melos versioning instead and documents the choice in an ADR with DX_FAQ commands. ## Quick Start Ask the agent to audit this repository's release process and recommend the appropriate changelog and versioning tooling for its ecosystem.

Frequently Asked Questions about release-changelog-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose release tooling for a monorepo?▼

Match the tool to the ecosystem: Changesets for pnpm or npm workspaces, Melos version for Dart monorepos, and release-plz or cargo-release for Rust workspaces. Record non-obvious choices in an ADR and document exact commands in DX_FAQ.

Changesets vs release-please for versioning?▼

Changesets fits monorepos where contributors write explicit release intent files per PR, while release-please generates release PRs from conventional commits. Choose Changesets for multiple publishable packages and release-please for single packages with commit-driven releases.

Should I use Changesets in a Rust or Dart repository?▼

No, Changesets is npm-centric and fits poorly outside JavaScript. Rust repos should use release-plz, cargo-release, or git-cliff, and Dart repos should use Melos or a manual CHANGELOG with git tags.

How do I distribute a CLI or MCP server binary?▼

Ship GitHub Release tarballs with SHA-256 checksums and a curl-friendly install.sh that detects platform, verifies checksums, and supports pinned versions. Avoid git clone as the end-user install path for server products.

Why does my tag push not trigger the release workflow?▼

GitHub suppresses recursive workflow triggers when a tag is pushed with the default GITHUB_TOKEN. Use a single release-owner workflow, authenticate with a PAT or GitHub App token, or trigger the binary workflow via workflow_run.

When should a repo not adopt Changesets?▼

Skip Changesets when the primary artifact is not npm, when a single package already releases cleanly via conventional commits, or when releases are binary and manifest driven. Forcing it adds an alien workflow contributors will ignore.

Related Skills

Explore More Software Engineering Skills→
svangesvange
1

ai-standardize-repo

Audits and fixes repository standards across pipelines, tooling, and governance using canonical policies.

Community
Advanced
SanHsienSanHsien
1

documentation-and-adrs

Writes architecture decision records, API documentation, READMEs, and changelogs for software projects.

Community
Intermediate
mikalvmikalv

release-plannotator

Prepares and executes Plannotator releases including notes, version bumps, builds, and tagging.

Community
Advanced
Arete-ConsortiumArete-Consortium
4

release-engineer

Automates release readiness checks, changelog generation, version tagging, and registry publishing for git repositories.

Official
Advanced