skillshare-changelog

Generate a CHANGELOG.md entry for a release. $ARGUMENTS specifies the tag version (e.g., `v0.16.0`) or omit to auto-detect via `git describe --tags --abbrev=0`. **Scope**: This skill updates `CHANGELOG.md` and syncs the website changelog (`website/src/pages/changelog.md`). It does NOT generate RELEASE_NOTES, update version numbers, or handle the full release workflow — use `/release` for that. ## Workflow ### Step 1: Determine Version Range ```bash # Auto-detect latest tag LATEST_TAG=$(git describe --tags --abbrev=0) # Find previous tag PREV_TAG=$(git describe --tags --abbrev=0 "${LATEST_TAG}^") echo "Generating changelog: $PREV_TAG → $LATEST_TAG" ``` ### Step 2: Collect Commits ```bash git log "${PREV_TAG}..${LATEST_TAG}" --oneline --no-merges ``` ### Step 3: Categorize Changes Group commits by conventional commit type: | Prefix | Category | |--------|----------| | `feat` | New Features | | `fix` | Bug Fixes | | `refactor` | Refactoring | | `docs` | Documentation | | `perf` | Performance | | `test` | Tests | | `chore` | Maintenance | ### Step 4: Read Existing Entries for Style Reference Before writing, read the most recent 2-3 entries in `CHANGELOG.md` to match the established tone and structure. The style evolves over time — always match the latest entries, not a hardcoded template. ### Step 5: Write User-Facing Entry Write from the **user's perspective**. Only include changes users will notice or care about. **Include**: - New features with usage examples (C...