Skip to main content
skill CX Codex

changelog · chrisbanes — Claude Code skill: what it does, how to install

A skill for Claude Code checks changelog entries against Git history and evidence from issues and PRs. It runs when preparing or reviewing release notes.

Apache-2.0 159 installs ★ 1,164 updated 2026-10-25

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

What changelog does

The skill updates or reviews a changelog using Git changes and related issues or PRs. It preserves accurate entries, adds missing user-facing changes, and leaves out internal ones. For notes tied to a release, the target version must be clear before editing.

Reviews are read-only: the skill presents findings or proposed notes without changing files. For authorized edits, it inspects the diff and runs git diff --check when command execution is allowed. It leaves Git mutations, version files, snapshots, and publication to the calling workflow.

What it helps with

  • compare changelog entries with Git history and code changes
  • find missing user-facing changes before a release
  • correct notes that lack support from issues or PRs
  • prepare changelog notes for a target version

Example prompts for the agent

  • Review the Unreleased changelog against Git history and related PRs.
  • Prepare changelog notes for version 2.0.0 from the changes and issues.
  • Check the links and author credits in the changelog entries.

How to install changelog

1Skills CLI (Vercel)

npx skills add chrisbanes/skills --skill changelog -a claude-code

2Manually: put the files in place

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

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

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

Questions about changelog

How do I install changelog in Claude Code?

Run npx skills add chrisbanes/skills --skill changelog -a claude-code. The skill file is at ~/.claude/skills/changelog/SKILL.md.

What does changelog do?

It checks changelog entries against Git history and evidence from issues and PRs. It can prepare release notes and review links, authorship, and coverage.

What does changelog need to work?

It does not require a Kotlin plugin, credentials, API snapshots, or release approval. For change review, it uses Git history and related evidence when available.

Source text

SKILL.md · Apache-2.0
---
name: changelog
description: Use when updating or reviewing Unreleased changelog entries, reconciling a changelog against Git history and issue or PR evidence, or preparing changelog notes for a specified release.
---

# Changelog

## Core principle

Keep consumer-visible notes complete and grounded in verified changes while
preserving curated wording and released history.

## Procedure

1. Establish the requested scope, repository conventions, changelog path and
   Git state. Choose **Unreleased maintenance** or **specified-release notes**;
   keep reviews read-only. If the user limits work to supplied state, run no
   discovery commands and mark unsupplied facts unknown. This skill applies
   across languages and publishing systems; it requires no Kotlin plugin,
   credentials, API snapshots or release approval.
   If no changelog exists and creation was not explicitly requested, report
   that it was skipped and finish. For explicitly requested creation, resolve
   its format and history scope first.
2. Establish the comparison range from repository tag conventions and ancestry,
   or supplied evidence. For Unreleased maintenance, compare against the latest
   applicable release, preserving the repository's incremental prerelease
   baseline. For specified-release notes, use the supplied target version;
   resolve a missing or ambiguous target before editing. For a specified
   prerelease, retain the repository's incremental baseline from the preceding
   applicable release. Keep an active prerelease cycle expanded. A final release uses
   the previous stable release as the baseline for the whole cycle, not only
   the latest RC delta; a first stable release covers history from the start.
   Resolve ambiguous tags rather than choosing the lexically highest one.
   Unreleased maintenance needs no next development version.
3. Compare existing notes with complete in-scope history, diffs and relevant
   issue/PR evidence. Preserve accurate curated wording; add missing
   consumer-visible changes, correct inaccuracies and omit internal-only
   changes. Attach each citation and credit only to an entry describing that
   change; give an uncovered change its own entry. Include relevant breaking
   changes and migration guidance. Resolve uncertain coverage or report the
   specific gap rather than inventing a claim or declaring completeness.
   For a final stable release, read [stable-release notes](references/stable-release.md)
   completely before editing and follow its coverage and history procedure.
4. Verify links and attribution. For each PR-supported change, link its number
   directly to the canonical pull URL, for example
   `[#123](https://github.com/OWNER/REPO/pull/123)`. Link matching issues where
   appropriate using explicit Markdown URLs; bare numbers are insufficient.
   For a verified non-maintainer PR author, include their verified name or
   username linked to their GitHub profile. Establish authorship from the PR
   and maintainer status from repository evidence. Supplied facts count as
   evidence; query a provider only when facts are missing and access is
   authorized. Report unverifiable URLs, authorship or maintainer status, and
   missing profile URLs for verified non-maintainers. Maintainers need no
   profile credit. Preserve accurate curated text apart from requested links
   and credit; never invent identities or classifications.
5. Apply only authorized changelog edits. Keep Unreleased maintenance under its
   existing heading. For specified-release notes, preserve repository heading,
   date and anchor conventions; finalize the heading only when requested.
   When called by `release-kotlin-library`, leave heading finalization to its
   release helper unless the caller explicitly requests changelog-only
   finalization. Leave Git mutations (including pulls and commits), version
   files, snapshots and publication to the caller. A reviewable changelog does
   not authorize those actions.
6. Inspect the actual diff against the reviewed changes, verify citation
   placement and preserved released history, and run `git diff --check` when
   command execution is permitted. Use repository documentation validation
   when required by its instructions or the changed formatting; report any
   unavailable validation. A heading check alone cannot establish semantic
   completeness.

## Finish gate

Show the actual notes or a directly reviewable diff, the comparison baseline and
reviewed scope, validation performed and unresolved evidence or coverage gaps.
For a read-only review, show findings or proposed notes without claiming edits.
For a missing changelog, report the skip without claiming reconciliation.
For a final release, verify every surviving coverage-ledger row appears in the
stable summary and the original prerelease history remains intact before
claiming the notes complete. Hand these results to the calling release workflow
when applicable; that caller owns remaining release gates and approval.

© chrisbanes · Apache-2.0 · chrisbanes/skills

Similar skills

All skills for Writing and docs →

changelog by other authors comes first.

changelog Donchitos Turns git commits and sprint records into two changelogs: one internal, one for players. Useful right before a release, when the notes still need writing. CX Codex +1 659installs changelog Remocn changelog gathers changes from git tags, commits, or merged pull requests, writes them as short human-readable updates, and feeds them into a video template. Use it when you need a quick announcement video for a new version. CX Codex +1 462installs changelog Shpigford Drafts customer-facing release notes from merged pull requests and inserts them directly into static site/changelog.html. CX Codex +1 135installs changelog pipecat-ai Builds changelog files for meaningful commits in a pull request. CX Codex +1 ★ 17,367repo stars changelog JetBrains changelog keeps IdeaVim’s CHANGES.md aligned with releases, commits, and pull requests, with entries written for users rather than maintainers. CX Codex +1 ★ 10,292repo stars changelog-automation Seth Hobson The changelog-automation skill helps generate changelogs and release notes from commits, PRs, and releases. Use it when setting up release workflows or shared commit rules. CX Codex +1 13,733installs changelog-writing Samuel Berthe changelog-writing turns raw commits, pull requests and tickets into release notes people actually read: what shipped, what it means, what breaks. CX Codex +1 13,400installs app-store-changelog Dimillian app-store-changelog — a skill for Claude Code, Codex, Cursor, and other agents that reads commits since the last git tag and writes user-facing App Store release notes. CX Codex +1 1,400installs utility-pm-changelog-curator product-on-purpose utility-pm-changelog-curator builds a CHANGELOG draft from git log and applies repository hygiene rules. Use it when banking unreleased work or preparing a release. CX Codex +1 683installs changelog-writer patricio0312rev changelog-writer turns git commits, PR titles and issue references into a CHANGELOG and release notes. Useful right before a release, when changes need sorting and a version number. CX Codex +1 631installs changelog-maintenance akillness The changelog-maintenance skill turns verified shipped work into changelog entries, release notes, migration updates, and small game patch notes. Use it after a release or patch. CX Codex +1 370installs

From the same set21

The whole set →
to-plan to-plan turns one GitHub issue or an in-chat task into an implementation plan with acceptance criteria. Useful when the work has to be handed to someone else. CX Codex +1 884installs run-github-project run-github-project runs a repository's GitHub Project workflow: triages Todo, claims work in Ready to implement, and carries it through to Done. CX Codex +1 829installs implement-with-subagents implement-with-subagents orchestrates plan tasks across solo or worker subagents with task-scoped commits, integration checks, and mandatory independent review. CX Codex +1 807installs grounded-writing grounded-writing — a skill for drafting and reviewing developer docs, reports, and replies without invented facts, promotional filler, or irrelevant implementation mechanics. CX Codex +1 660installs android-benchmark-comparison android-benchmark-comparison enforces a reproducible procedure for comparing physical Android benchmark configurations. Helps resolve reversed rankings and pick measured defaults safely. CX Codex +1 559installs release-kotlin-library release-kotlin-library is a Claude Code skill that prepares, validates, and publishes Kotlin library releases. It checks changelogs and Metalava API snapshots before publication. CX Codex +1 559installs deliver-spec deliver-spec takes an approved GitHub issue or local specification and delivers it through a validated pull request. Useful when delegating implementation with mandatory independent review. CX Codex +1 359installs subagent-delegation The subagent-delegation skill for Claude Code manages subagent task distribution and reassignment. It runs when the user invokes the playbook or explicitly requests delegation. CX Codex +1 123installs

Project sponsors

Companies that keep this analytics open