Stats
Actions
Tags
From overcode
Generates or updates CHANGELOG.md from git history following the Keep a Changelog format, commits the changelog, and creates a signed annotated tag. Use when a user wants to release or document changes: "generate changelog", "update CHANGELOG", "release v1.2.0", "tag this version", "what changed since last release". Do NOT use for writing release notes in a format other than Keep a Changelog, managing GitHub Releases UI, or bumping version numbers in package.json or Cargo.toml — this skill only manages CHANGELOG.md and git tags.
How this skill is triggered — by the user, by Claude, or both
Slash command
/overcode:changeloghaikuThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Changelog reads the git log since the last tag, groups commits by Keep a Changelog category, prepends a new version section to `CHANGELOG.md`, commits the file, and creates an annotated tag.
Changelog reads the git log since the last tag, groups commits by Keep a Changelog category, prepends a new version section to CHANGELOG.md, commits the file, and creates an annotated tag.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | generate | Gather commits → group → write CHANGELOG.md → commit → tag | Version string ($ARGUMENTS, optional) |
Single action. Dispatch to generate on any trigger.
chore, style, and ci commits unless they are significant (e.g., a major CI overhaul).CHANGELOG.md.YYYY-MM-DD format.CHANGELOG.md; never overwrite the full file.feat → minor, fix → patch, BREAKING CHANGE footer → major.aidd_docs/templates/vcs/commit.md — commit message conventions for this projectnpx claudepluginhub rebellioussmile/my-claude-marketplace --plugin overcodeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.