$npx -y skills add tobihagemann/turbo --skill create-changelogCreate a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"initialize changelog\", \"start a changelog\", \"set up changelog\", \"generat
| 1 | # Create Changelog |
| 2 | |
| 3 | Create a changelog backfilled with version history. |
| 4 | |
| 5 | ## Step 1: Run `/changelog-rules` Skill |
| 6 | |
| 7 | Run `/changelog-rules` to load shared changelog conventions. |
| 8 | |
| 9 | ## Step 2: Backfill Version History |
| 10 | |
| 11 | Collect release history from the most authoritative source available: |
| 12 | |
| 13 | 1. **GitHub releases** (preferred): Run `gh release list --limit 100 --json tagName,name,publishedAt,body` to get release notes. For each release, parse the body into changelog entries. |
| 14 | 2. **Git tags** (fallback): If no GitHub releases exist, run `git tag --sort=-v:refname` to list tags. For each consecutive tag pair, run `git log <older-tag>..<newer-tag> --oneline` to collect commit summaries. |
| 15 | |
| 16 | For each version, classify entries into the standard change types and apply the changelog-worthiness criteria per `/changelog-rules`. |
| 17 | |
| 18 | ## Step 3: Check for Existing Changelog |
| 19 | |
| 20 | If the changelog file already exists, warn the user and confirm before overwriting. |
| 21 | |
| 22 | ## Step 4: Write Changelog |
| 23 | |
| 24 | Write the changelog following the `/changelog-rules` file structure and conventions. |
| 25 | |
| 26 | ## Step 5: Present the Result |
| 27 | |
| 28 | Briefly summarize how many versions were backfilled and which source was used (GitHub releases or git tags). |