SkillAgentSearch skills...

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.

Install / Use

npx skills add runkids/skillshare --skill skillshare-changelog

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of skillshare-changelog

skillshare-changelog scores 88/100 on our quality scale, 1526th of 2,790 Automation skills we index.

Its SKILL.md is 5.1 KB long, well organised into 18 sections with 3 code examples: a solid amount of guidance for an agent.

With 2,689 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so skillshare-changelog is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

skillshare-changelog compared with similar skills

All 4 of these similar skills score higher than skillshare-changelog; compare them before choosing.

SkillScoreStarsUpdatedFormat
skillshare-changelog (this skill)by runkids882.7k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install skillshare-changelog?
Run npx skills add runkids/skillshare --skill skillshare-changelog. The install tabs above show the steps for each supported agent.
Which AI agents does skillshare-changelog work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is skillshare-changelog safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is skillshare-changelog still maintained?
The repository was last updated about 2 months ago, so skillshare-changelog is actively maintained.

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 (tests, changelog, release notes, version bump, announcements), use /release instead. argument-hint: "[tag-version]" metadata: targets: [claude, universal]

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.

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

# 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

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 (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

Read existing CHANGELOG.md and insert new entry at the top, after the header. Match the style of the most recent entries exactly.

Structural conventions (based on actual entries):

## [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

**How to sync**: Read the website changelog, then insert the same new entry after the `---` separator (line after intro paragraph), before the first existing version entry. Do NOT replace the entire file — only insert the new entry block.

## Rules

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

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryAutomation
Updated1mo ago
Forks167

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions