release-changelog-harness

Installation
SKILL.md

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 lens Verdict on “use JS Changesets everywhere”
JS monorepo maintainer Strong default: .changeset/*.md + changeset version beats hand-editing five package.json files.
Dart / Flutter publisher Weak fit as-is: pub uses tags + CHANGELOG.md; monorepos often use Melos version / changelog, not npm Changesets.
Rust / Go shipper Use release-plz, cargo-release, or git-cliff—forcing Changesets adds alien workflow.
Agent operator Wins 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 charter Teach when + gate + doc placement; link to upstream docs; do not paste 200-line configs into SKILL.md.

Improved framing (use this):

Related skills

More from arenukvern/skill_steward

Installs
1
GitHub Stars
1
First Seen
1 day ago
release-changelog-harness — arenukvern/skill_steward