skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync. For full release workflows (tests, changelog, release notes, version bump, announcements), use /re
npx skills add runkids/skillshare --skill skillshare-changelog --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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 ton
- Workflow
- Step 1: Determine Version Range
- Step 2: Collect Commits
- Step 3: Categorize Changes
- Step 4: Read Existing Entries for Style Reference
- Step 5: Write User-Facing Entry
- Step 6: Update CHANGELOG.md
- Step 7: Sync Website Changelog
- Rules
Auto-detect latest tag
Find previous tag
echo "Generating changelog: $PREV_TAG → $LATEST_TAG"
git log "${PREV_TAG}..${LATEST_TAG}" --oneline --no-mergesWhat does the skillshare-changelog skill do?
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync. For full release workflows (tests, changelog, release notes, version bump, announcements), use /re
How do I install it?
Run `npx skills add runkids/skillshare --skill skillshare-changelog --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From runkids/skillshare, a repository with 2,519 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.