changeloglisted
Install: claude install-skill real-case/marvin-toolkit
# Changelog Generator
Generate a structured, user-facing changelog from git commit history.
## Step 1: Determine the commit range
Run these commands to understand the repo state:
```bash
# Available tags (most recent first)
git tag --sort=-version:refname | head -20
# Current branch
git rev-parse --abbrev-ref HEAD
# Total commit count on current branch
git rev-list --count HEAD
```
Then determine the range based on user input:
| User says | Range to use |
|---|---|
| Specific tags: "v1.0 to v1.1" | `v1.0..v1.1` |
| "Since last release" | `$(git describe --tags --abbrev=0)..HEAD` |
| Date range: "last 2 weeks" | `--since="2 weeks ago"` |
| "All unreleased changes" | `<latest-tag>..HEAD` |
| No tags exist at all | Ask user for a date range, or use `--since="1 month ago"` as default |
If the range contains **more than 200 commits**, warn the user and suggest narrowing the range or generating a high-level summary instead of per-commit entries.
## Step 2: Collect and analyze commits
```bash
# Detailed log with hash, subject, body, and author
git log <range> --no-merges --format="---commit---%n%H%n%s%n%b%n---%an"
# If the project uses PR-based workflow, also check merge commits for PR context
git log <range> --merges --format="%s" | head -20
```
Extract PR/issue numbers from commit subjects — common patterns: `(#123)`, `[#123]`, `fixes #123`, `closes #123`, `PROJ-456`.
If the project has **scoped conventional commits** (e.g. `feat(api):`, `fix(ui):`), note the scopes