Agent skill

Skillshare Changelog

by runkids in runkids/skillshare

Generate CHANGELOG.md entry from recent commits in conventional format.

MITAuto-check passedDevelopment

Install Skillshare Changelog

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install runkids/skillshare skillshare-changelog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/runkids/skillshare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skillshare/skills/skillshare-changelog .claude/skills/skillshare-changelog && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
skillshare-changelog
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
563 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Generate CHANGELOG.md entry from recent commits in conventional format.

  • Works in 6 steps: Determine Version Range → Collect Commits → Categorize Changes → …
  • The user asks to: generate a changelog
  • SKILL.md covers Workflow and Rules
  • Calls python3 and git

What it does

Skillshare Changelog is an agent skill from runkids/skillshare. 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…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Pull requests. The repository describes itself as: 📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing. The licence is MIT.

When your agent uses it

  • The user asks to: generate a changelog
  • Document what changed between tags
  • Create a new CHANGELOG entry

Example prompts

  • “write the changelog for v0.17”
  • “what changed since last release”
  • “/skillshare-changelog”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Determine Version Range
  2. Collect Commits
  3. Categorize Changes
  4. Read Existing Entries for Style Reference
  5. Write User-Facing Entry
  6. Update CHANGELOG.md

What it can do on your machine

Read from SKILL.md and the folder at commit 5e3840e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Skillshare Changelog loads about 1.6k tokens when it runs. Until then it costs about 160 tokens; SKILL.md has 563 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~160
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from runkids/skillshare at commit 5e3840e, republished under its MIT licence (© runkids). 563 words, ~1,566 tokens.

Download SKILL.mdSave it as .claude/skills/skillshare-changelog/SKILL.md (or your agent's skills folder).
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:

PrefixCategory
featNew Features
fixBug Fixes
perfPerformance
breaking changeBreaking Changes and migration notes
revertReverts, 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
Show full SKILL.md (173 more words)Show less
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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .skillshare/skills/skillshare-changelog of runkids/skillshare.

Open the folder on GitHubat commit 5e3840e

Compare with similar skills

Skillshare Changelog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Skillshare Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skillshare Changelog this skillrunkids/skillshare2.8k—~1.6kAutomated safety check: PassMIT
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
Changesetbiomejs/biome26k—~839Automated safety check: PassApache-2.0
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
pybind11 Release Preparationpybind/pybind1118k—~1.7kAutomated safety check: PassCustom licence

Similar skills

  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • Changeset

    biomejs/biome

    Official

    A skill your agent uses when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit .changeset/.md release-note text.

    26k GitHub stars~839 tokensUpdated today
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.

    18k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • AionUi Version Bump

    iOfficeAI/AionUi

    Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.

    33k GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from runkids/skillshare

  • Skillshare

    runkids/skillshare

    Manage skills, agents, extras, hooks, plugins, and MCP connection settings with the Skillshare CLI.

    2.8k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Skillshare UI Website Style

    runkids/skillshare

    Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/).

    2.8k GitHub stars~4.5k tokensUpdated today
    Auto-check passed
  • Skillshare Release

    runkids/skillshare

    Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when…

    2.8k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Skillshare Windows Utm

    runkids/skillshare

    Verify skillshare on a real Windows guest running in local UTM: build a pinned commit in the devcontainer, push it into the VM, and either run the Windows E2E runbook with full and basic-user tokens…

    2.8k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Skillshare Changelog

What does Skillshare Changelog do?

Generate CHANGELOG.md entry from recent commits in conventional format. Skillshare Changelog is an agent skill from runkids/skillshare.md entry from recent commits in conventional format.

When should I use Skillshare Changelog?

Skillshare Changelog fits situations like: the user asks to: generate a changelog; document what changed between tags; create a new CHANGELOG entry.

How do I install Skillshare Changelog in Claude Code?

Run `npx skills add runkids/skillshare --skill skillshare-changelog -a claude-code`. Or copy the skill folder (.skillshare/skills/skillshare-changelog in runkids/skillshare) into .claude/skills/skillshare-changelog in your project. Claude Code loads it when a task matches its description.

How do I install Skillshare Changelog in Codex?

Run `npx skills add runkids/skillshare --skill skillshare-changelog -a codex`. Or copy the skill folder (.skillshare/skills/skillshare-changelog in runkids/skillshare) into .agents/skills/skillshare-changelog in your project. Codex loads it when a task matches its description.

Can I use Skillshare Changelog in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add runkids/skillshare --skill skillshare-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skillshare-changelog, .gemini/skills/skillshare-changelog, .github/skills/skillshare-changelog and .opencode/skills/skillshare-changelog in your project.

What does Skillshare Changelog need to run?

Going by SKILL.md and its folder, Skillshare Changelog needs the command-line tools its instructions call (python3 and git). Our summary lists: Python 3.

Does Skillshare Changelog access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Skillshare Changelog safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Skillshare Changelog use?

Skillshare Changelog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skillshare Changelog use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Skillshare Changelog?

Skills that share tags, products or a category with Skillshare Changelog: StarRocks Release Notes (StarRocks/starrocks, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), Changeset (biomejs/biome, 26k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skillshare Changelog?

runkids (a GitHub user) maintains it in runkids/skillshare, which has 2,755 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: runkids/skillshare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.