changelog

Maintains CHANGELOG.md in Keep a Changelog format with add, release, audit, and backfill operations.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/chris-prener/dev-kit --skill changelog-chris-prener
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/chris-prener/dev-kit/tree/main/dev-kit/skills/changelog
Command: npx skills add https://github.com/chris-prener/dev-kit --skill changelog-chris-prener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a user-facing changelog accurate and complete is tedious: entries get forgotten when PRs merge, releases require manual reformatting, and retroactive coverage checks are rarely done. This Skill automates the four core changelog operations so CHANGELOG.md stays consistent with Keep a Changelog 1.1.0 conventions. ## Core Features & Use Cases - Add entries: Append categorized bullets (Added, Changed, Deprecated, Removed, Fixed, Security) under the [Unreleased] section with PR/issue references. - Cut releases: Rename [Unreleased] to a versioned, dated block and open a fresh empty [Unreleased] section above it. - Audit coverage: Query merged PRs via the GitHub CLI with paginated search and report any PRs missing changelog entries. - Backfill entries: Draft one-line entries for past PRs using label and title heuristics, surfaced for human review before writing. - Use Case: Before cutting release v2.3.0, run an audit to find merged PRs since v2.2.0 lacking entries, backfill the gaps, then cut the release in one workflow. ## Quick Start Ask the assistant to add a changelog entry for the current PR, audit changelog coverage since the last release, or cut a new release version.

Frequently Asked Questions about changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a changelog entry for a pull request?▼

Provide the category (Added, Changed, Deprecated, Removed, Fixed, or Security), a one-sentence user-facing description, and the PR or issue number. The entry is appended as a bullet under the matching subsection of the [Unreleased] block in CHANGELOG.md.

How do I cut a release in Keep a Changelog format?▼

Supply the target version number and optionally a release date. The [Unreleased] block is renamed to [X.Y.Z] — YYYY-MM-DD and a fresh empty [Unreleased] section with all six categories set to _None._ is inserted above it.

How can I check if merged PRs are missing changelog entries?▼

Run the audit operation with an optional cutoff date. It queries merged PRs via the GitHub CLI using paginated search, then reports any PRs not referenced in the [Unreleased] block of CHANGELOG.md.

Does the changelog audit miss PRs due to GitHub CLI limits?▼

No. The audit uses gh api --paginate with the search/issues endpoint instead of gh pr list, which truncates at 30 results. This ensures complete coverage of merged PRs since the cutoff date.

When should a change skip the changelog?▼

Internal-only changes with no user-facing surface should skip the changelog using the no-changelog label opt-out on the PR. The skill is not for cross-repo aggregation, auto-generated entries without review, or automatic version bumping.