SkillAgentSearch skills...

changelog-generator

Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes

Install / Use

npx skills add borghei/Claude-Skills --skill changelog-generator

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of changelog-generator

changelog-generator scores 84/100 on our quality scale, 2098th of 2,769 Automation skills we index.

Its SKILL.md is 6.4 KB long, well organised into 9 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
13/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so changelog-generator is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. 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-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

changelog-generator compared with similar skills

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

SkillScoreStarsUpdatedFormat
changelog-generator (this skill)by borghei8481757d agoSKILL.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
Scraplingby D4Vinci100103.9ktodayMCP Server

Frequently asked questions

How do I install changelog-generator?
Run npx skills add borghei/Claude-Skills --skill changelog-generator. The install tabs above show the steps for each supported agent.
Which AI agents does changelog-generator 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 changelog-generator 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 declares no license and scores 88/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 changelog-generator still maintained?
The repository was last updated about 2 months ago, so changelog-generator is actively maintained.

name: changelog-generator description: > Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes. license: MIT + Commons Clause metadata: version: 1.1.0 author: borghei category: engineering domain: release-management tier: POWERFUL updated: 2026-06-17 frameworks: conventional-commits, keep-a-changelog, semantic-versioning

Changelog Generator

Generate consistent, auditable changelogs and release notes from Conventional Commits. Parses commit messages, detects semantic version bumps (major/minor/patch), renders Keep a Changelog sections, supports monorepo scoped changelogs, integrates with CI for automated release notes, and enforces commit format with linting. Separates commit parsing, bump logic, and rendering so teams can automate releases without losing editorial control.

Keywords

changelog, release notes, conventional commits, semantic versioning, semver, Keep a Changelog, commit linting, release automation, monorepo changelog

Core Capabilities

  • Commit parsing — parse Conventional Commit messages into structured data (type, scope, description, body, footer); detect breaking changes from ! and BREAKING CHANGE:.
  • Semantic version detection — map commit types to bump levels (breaking→major, feat→minor, others→patch); support pre-release versions.
  • Changelog rendering — Keep a Changelog, GitHub release notes, plain markdown, and JSON output grouped by type.
  • Quality enforcement — commit message linter for CI and pre-commit hooks, strict mode, scope validation, breaking-change documentation requirements.

When to Use

  • Before publishing a release tag
  • During CI to generate release notes automatically
  • In PR checks to enforce commit message standards
  • In monorepos where package changelogs need scoped filtering
  • When converting raw git history into user-facing notes
  • As a pre-release checklist step

Clarify First

Before generating the changelog, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Commit range — since which tag or commit (defines what history is included)
  • [ ] Output format — Keep a Changelog, GitHub release notes, plain markdown, or JSON (sets changelog_formatter.py --format)
  • [ ] Version & scope — the release version, and in a monorepo which package scope to filter (sets --version and scoped filtering)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

| Tool | Purpose | Command | |------|---------|---------| | commit_parser.py | Parse git log (with ---COMMIT_END--- delimiters) into structured changelog entries | git log --pretty=format:'%H%n%s%n%b%n---COMMIT_END---' --no-merges \| python scripts/commit_parser.py --json | | breaking_change_detector.py | Scan commit messages/diffs for breaking-change indicators | python scripts/breaking_change_detector.py -f gitlog.txt --severity high | | changelog_formatter.py | Format parsed commits into Keep a Changelog or GitHub markdown | python scripts/changelog_formatter.py -f parsed.json --version 1.4.0 --format keepachangelog |

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/commit-format-and-rendering.md — the Conventional Commit grammar, type→section/semver mapping table, breaking-change rules, and the Keep a Changelog and GitHub Release Notes output formats. Read when defining commit standards or output style.
  • references/generation-and-linting.md — the 4-step parse→bump→render workflow with Python code, the pre-commit hook and CI commitlint config, monorepo scoped-changelog strategy, and the release-workflow integration diagram. Read when building the pipeline or enforcing format.
  • references/quality-and-troubleshooting.md — the pre-publish quality checklist, common pitfalls, best practices, troubleshooting table, and success criteria. Read before publishing a changelog or when diagnosing an issue.

Scope & Limitations

This skill covers:

  • Parsing Conventional Commit messages into structured data for changelog generation
  • Determining semantic version bumps (major/minor/patch) from commit history
  • Rendering changelogs in Keep a Changelog, GitHub Release Notes, plain markdown, and JSON formats
  • Enforcing commit message standards via pre-commit hooks and CI linting

This skill does NOT cover:

  • Actual release publishing or deployment pipeline execution — see engineering/ci-cd-pipeline-design
  • Git tag management, branch strategies, or merge workflows — see engineering/git-workflow-automation
  • Writing or improving commit messages themselves — see standards/git/git-workflow-standards.md
  • Coordinated multi-package versioning with tools like Changesets or Lerna — referenced in monorepo strategy but not implemented here

Integration Points

| Skill | Integration | Data Flow | |-------|-------------|-----------| | engineering/ci-cd-pipeline-design | Changelog generation runs as a CI stage before release publishing | Parsed commits and rendered changelog feed into the release pipeline as artifacts | | engineering/git-workflow-automation | Commit linting hooks enforce format before commits reach the changelog generator | Pre-commit validation ensures only parseable commits enter the git history | | engineering/code-review-automation | PR checks verify commit messages conform to Conventional Commits before merge | Linting results gate PR approval, preventing unparseable commits from reaching main | | engineering/api-versioning-strategy | Breaking change detection aligns API version bumps with changelog major releases | BREAKING CHANGE commits trigger both changelog entries and API version increments | | project-management/release-management | Release planning uses generated changelogs for stakeholder communication | Rendered release notes flow into release checklists and stakeholder announcements | | standards/git/git-workflow-standards.md | Commit format standards define the grammar this skill parses | Standard definitions are the source of truth for the commit regex pattern |

Related Skills

View on GitHub
GitHub Stars817
CategoryAutomation
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/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.

1 medium
changelog-generator — Universal Skill: Install & Safety Check | SkillAgent