← ClaudeAtlas

changeloglisted

Use when the user wants to generate a changelog, release notes, or document what changed between versions, tags, or PRs
AlemTuzlak/skills · ★ 39 · AI & Automation · score 74
Install: claude install-skill AlemTuzlak/skills
# Changelog Generator Auto-generate human-friendly changelogs from git history. Follows Keep a Changelog format, polishes commit messages into user-friendly language, and optionally creates GitHub Releases. ## Input Resolution The primary input is a git ref range. Resolve the argument (if provided): 1. Contains `...` or `..` -> **git ref range** (e.g. `v1.0.0...v1.1.0`) 2. Matches a single tag/ref -> **from that ref to HEAD** 3. Matches GitHub URL or `#\d+` pattern -> **PR** (extract changes from that PR only). For single PR input: read the PR diff and description, categorize changes, use the PR title as the entry. Skip the version header. Ask the user if they want to append these entries to an existing changelog version or create a new one. 4. No argument -> ask: "What range should the changelog cover? You can provide a git ref range (e.g. v1.0.0...v1.1.0), a tag (changes since that tag), or a PR number." ## Process Flow ```dot digraph changelog { rankdir=TB; "Resolve input" [shape=box]; "Phase 1: Gather" [shape=box]; "Phase 2: Categorize" [shape=box]; "Phase 3: Polish" [shape=box]; "Phase 4: Review" [shape=box]; "Approved?" [shape=diamond]; "Phase 5: Output" [shape=box]; "Resolve input" -> "Phase 1: Gather"; "Phase 1: Gather" -> "Phase 2: Categorize"; "Phase 2: Categorize" -> "Phase 3: Polish"; "Phase 3: Polish" -> "Phase 4: Review"; "Phase 4: Review" -> "Approved?"; "Approved?" -> "Phase 3: Polish" [label="revi