What problem does it solve? Projects often lack a consistent changelog, reliable version bumps, or a defined release policy β the bump gets forgotten on hand-commits, tags diverge from package.json, and nobody knows which merge triggers a release. This Skill installs a standardized Keep-a-Changelog + SemVer setup with a fail-loud CI gate and a configurable branch/merge/release policy. ## Core Features & Use Cases - Two mutually exclusive mechanisms: Mechanism A (hand-written CHANGELOG.md plus a dependency-free version-bump.mjs script and a fail-loud CI guard) as the default, or Mechanism B (Changesets) for monorepos with per-package versioning β the bump script refuses to run when both coexist. - Ready-to-wire scaffolding assets: CHANGELOG template with compare-footer links, commitlint config enforcing Conventional Commits, a changelog-guard GitHub Actions workflow, and a SemVer bump script that derives major/minor/patch from commit history. - Configurable release policy: Default trunk-based model (squash to main, deliberate human tagging) or opt-in Gitflow with prerelease channels, documented in the project's CLAUDE.md. - Use Case: A team whose releases constantly drift out of sync invokes the Skill to install the changelog template, wire the pre-commit bump hook and CI gate, and verify the gate actually fails when code ships without an [Unreleased] entry. ## Quick Start Ask the agent to set up changelog, versioning, and release automation in this repository using the setup-changelog skill.
