Skip to main content
skill CX Codex

skillshare-changelog — Claude Code skill: what it does, how to install

skillshare-changelog turns the commits between two tags into a CHANGELOG.md entry and copies it to the project's website changelog page.

MIT ★ 3,269 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add runkids/skillshare --skill skillshare-changelog -a claude-code
Open on GitHub

What skillshare-changelog does

The skill reads commits from the last published tag up to the head of the Release PR, sorts them by conventional commit type and writes the result into CHANGELOG.md. feat lands in New Features, fix in Bug Fixes, perf in Performance; breaking changes get their own block with migration notes. Test-only, CI and docs commits stay out of the published notes.

It does not pick or bump a version. That comes from .github/release-please-manifest.json on the Release PR branch, and before acting the skill asks for python3 scripts/ai-context.py release, the topic that carries the authorization and sync rules. Wording and layout are matched against the 2-3 most recent entries in CHANGELOG.md.

Then python3 scripts/release/release.py sync and check, run inside the devcontainer, copy the newest entry to website/src/pages/changelog.md and leave the frontmatter and older entries alone. Publishing, tags and announcements are out of scope — that is what /release handles.

What it helps with

  • turn a range of commits into a CHANGELOG.md entry
  • sort commits into New Features, Bug Fixes and Performance sections
  • rewrite the change history so users can read it
  • mirror the new entry onto the website changelog page
  • keep tests, CI and docs edits out of the published notes

Example prompts for the agent

  • Write the changelog for v0.17 from the commits since the last tag
  • What changed since the last release? Draft a new CHANGELOG entry.
  • Update CHANGELOG.md and sync website/src/pages/changelog.md

How to install skillshare-changelog

1Skills CLI (Vercel)

npx skills add runkids/skillshare --skill skillshare-changelog -a claude-code

2Manually: put the files in place

~/.claude/skills/skillshare-changelog/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/skillshare-changelog/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about skillshare-changelog

How do I install skillshare-changelog in Claude Code?

Run npx skills add runkids/skillshare --skill skillshare-changelog -a claude-code. The skill file ends up at ~/.claude/skills/skillshare-changelog/SKILL.md.

What does skillshare-changelog do?

It collects commits for a given tag range, groups them by conventional commit type and writes a user-facing entry into CHANGELOG.md. The same entry is then mirrored to the website changelog page.

Does it need Python?

Yes. The skill starts with python3 scripts/ai-context.py release, and the website sync runs python3 scripts/release/release.py sync plus check in the devcontainer.

Source text

SKILL.md · MIT
---
name: skillshare-changelog
description: >-
  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 (Release PR review, tests, draft assets, publication, announcements),
  use /release instead.
argument-hint: "[tag-version]"
metadata:
  targets: [claude, universal]
---

Review or generate a user-facing changelog entry. Prefer the open Release Please PR and its manifest version for an upcoming release. For historical work, $ARGUMENTS specifies the requested tag or commit range.

**Scope**: This skill updates `CHANGELOG.md` and syncs the website changelog (`website/src/pages/changelog.md`). It does NOT generate RELEASE_NOTES, choose a new version, or handle the full release workflow — use `/release` for that.

Before acting, run `python3 scripts/ai-context.py release`. That topic is the source of truth for authorization, changelog content and synchronization rules; this skill retains the entry-generation workflow.

## Workflow

### Step 1: Determine Version Range

For an upcoming release, work on the Release PR branch and read `.github/release-please-manifest.json`. Verify the latest published tag and use its range to the Release PR head. Keep the proposed version; this skill does not authorize a version change. Tags may exist for unpublished drafts, so do not assume the highest local tag is the latest published release.

For historical work, use the user-requested tags or range.

### Step 2: Collect Commits

```bash
git log <previous-published-tag>..<release-pr-head-or-requested-tag> --oneline --no-merges
```

Review the generated Release Please entry before writing. Preserve useful manual examples and migration notes. Do not add a second entry for the same version.

### Step 3: Categorize Changes

Group commits by conventional commit type:

| Prefix | Category |
|--------|----------|
| `feat` | New Features |
| `fix` | Bug Fixes |
| `perf` | Performance |
| breaking change | Breaking Changes and migration notes |
| `revert` | Reverts, when user-visible |

Exclude test-only, CI-only, pure refactoring, documentation-only and internal maintenance entries from published notes.

### 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 (CLI commands, code blocks)
- Bug fixes that affected user-visible behavior
- Breaking changes (renames, removed flags, scope changes)
- Performance improvements users would notice

**Exclude**:
- Internal test changes (smoke tests, test refactoring)
- Implementation details (error propagation, internal structs)
- Dev toolchain changes (Makefile cleanup, CI tweaks)
- Pure documentation adjustments

**Wording guidelines**:
- Don't use "first-class", "recommended" for non-default options
- Be factual: "Added X" / "Fixed Y" / "Renamed A to B"
- Include CLI example when introducing a new feature
- Use em-dash (`—`) to separate feature name from description
- Group related features under `####` sub-headings when there are 2+ distinct areas

### Step 6: Update CHANGELOG.md

Edit the existing generated entry on the Release PR branch. If the requested historical entry does not exist, insert it at the appropriate position. Match the style of the most recent entries.

Structural conventions (based on actual entries):
```markdown
## [X.Y.Z] - YYYY-MM-DD

### New Features

#### Feature Area Name

- **Feature name** — description with `inline code` for commands and flags
  ```bash
  skillshare command --flag    # usage example
  ```
  Additional context as sub-bullets or continuation text

#### Another Feature Area

- **Feature name** — description

### Bug Fixes

- Fixed specific user-visible behavior — with context on what changed
- Fixed another issue

### Performance

- **Improvement name** — description of what got faster

### Breaking Changes

- Renamed `old-name` to `new-name`
```

Key style points:
- Version numbers use `[X.Y.Z]` without `v` prefix in the heading
- Feature bullets use `**bold name** — em-dash description` format
- Code blocks use `bash` language tag for CLI examples
- Bug fixes describe the symptom, not the implementation
- Only include sections that have content (skip empty Performance, Breaking Changes, etc.)

### Step 7: Sync Website Changelog

The website has its own changelog page at `website/src/pages/changelog.md`. After updating `CHANGELOG.md`, sync the new entry to the website version.

**Differences between the two files**:
- Website file has MDX frontmatter (`title`, `description`) and an intro paragraph — preserve these, don't overwrite
- Website file has a `---` separator after the intro, before the first version entry
- The release entries themselves are identical in content

For an upcoming Release PR, run inside the devcontainer:

```bash
python3 scripts/release/release.py sync
python3 scripts/release/release.py check
```

The helper normalizes the generated version heading, replaces or prepends only the newest website entry, and synchronizes the built-in skill metadata to the already proposed manifest version. It preserves website frontmatter, intro and historical entries. It does not choose or bump a version.

For historical corrections, edit the matching entry in both files directly; the helper handles only the current manifest release. Review the diff and run `python3 scripts/ai-context.py check`.

## Rules

Apply the `release` topic. This adapter is changelog-only and does not broaden authorization to commit, tag, push or publish.

© runkids · MIT · runkids/skillshare

Similar skills

All skills for Git and GitHub →

From the same set10

The whole set →
skillshare-update-docs skillshare-update-docs syncs skillshare website documentation with recent Go code changes and validates every CLI flag against source files. Useful right after shipping new flags. CX Codex +1 ★ 3,269repo stars skillshare-code-review skillshare-code-review is a Claude Code skill that reviews changes in skillshare before a pull request or after one opens. It starts on requests to inspect a diff, branch, commit range, or PR. CX Codex +1 ★ 3,269repo stars skillshare-windows-utm skillshare-windows-utm is a Claude Code skill that tests skillshare in a local UTM Windows guest, building pinned commits in a devcontainer and checking symlinks, junctions, and copy fallbacks. CX Codex +1 ★ 3,269repo stars skillshare-implement-feature The skillshare-implement-feature skill takes a Go feature from a spec or plain description through TDD and verification. Use it for CLI commands, flags, and internal packages. CX Codex +1 ★ 3,269repo stars skillshare-devcontainer skillshare-devcontainer runs the skillshare CLI, Go tests and the web dashboard inside the project's devcontainer, so macOS never silently mangles a command. CX Codex +1 ★ 3,269repo stars skillshare-release Coordinates and verifies skillshare releases through Release Please PRs, syncs documentation across locales, and inspects draft assets. CX Codex +1 ★ 3,269repo stars skillshare This skill guides Skillshare CLI workflows for syncing resources, checking configuration, and managing shared memory. Use it when setting up a project or user-wide environment. CX Codex +1 ★ 3,269repo stars skillshare-ui-website-style skillshare-ui-website-style keeps the Skillshare design system in place across a React dashboard and a Docusaurus site. Useful when you touch styles or add a component and want it to match. CX Codex +1 ★ 3,269repo stars

Project sponsors

Companies that keep this analytics open