← ClaudeAtlas

changelog-from-prslisted

Draft a release changelog by summarizing merged pull requests since the last tag. Use when preparing a release or writing release notes.
imtiazrayhan/agentscamp-library · ★ 1 · AI & Automation · score 75
Install: claude install-skill imtiazrayhan/agentscamp-library
Turn a range of merged pull requests into a clean, human-readable changelog. This skill collects the PRs merged since the previous release tag, groups them by change type (features, fixes, breaking changes, and more), and drafts release notes that are accurate, scannable, and ready to paste into a GitHub release or `CHANGELOG.md`. ## When to use this skill - You are cutting a new release and need release notes that reflect what actually shipped. - You want a first draft of a `CHANGELOG.md` entry that follows [Keep a Changelog](https://keepachangelog.com/) conventions. - You need to summarize a noisy list of merge commits into something a human reader can understand. - You are reviewing what changed between two tags before deciding on a version bump. > [!NOTE] > This skill drafts notes from real PR data. It does not push tags or publish releases. Always review the draft before publishing. ## Instructions 1. **Find the last release tag.** Use the most recent semantic-version tag as the lower bound. If no tag exists, fall back to the first commit. ```bash git describe --tags --abbrev=0 ``` 2. **Collect merged PRs in the range.** Prefer the GitHub CLI so you get titles, numbers, authors, and labels. Use the merge date of the last tag as the cutoff. ```bash LAST_TAG=$(git describe --tags --abbrev=0) SINCE=$(git log -1 --format=%cI "$LAST_TAG") gh pr list --state merged --base main --limit 200 \ --search "merged:>$SINCE" \ --json number,title,