Skip to main content
Agent skill

Changelog

Generate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks to prepare a changelog for a version like "changelog for 0.5.3".

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Changelog when an AI agent needs a reusable SKILL.md workflow for this job: Generate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks to prepare a changelog for a version like "changelog for 0.5.3".

When not to use it

Skip Changelog when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/changelog
# Save SKILL.md to ~/.claude/skills/changelog/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/changelog/SKILL.md. For a shared project, commit the folder at .claude/skills/changelog/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Changelog skill for this task: Use Changelog when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Changelog Generation

Generate a changelog entry for a new release by analyzing merged PRs since the last tag.

## Parameters

The user provides: - **Version number** -- e.g., `0.5.3` - **Additional PRs** -- optionally, PRs not yet merged that should be included

## Step 1: Gather Data

1. Find the previous release tag: `git tag --sort=-version:refname | head -1` 2. List all merge commits since that tag: `git log <tag>..HEAD --merges --format='%s' | grep -v "Merge branch"` 3. Get PR details with: `gh pr list --state merged --base main --search "merged:><tag-date>" --json number,title,author --limit 50` 4. List contributors: `git log <tag>..HEAD --format='%an' --no-merges | sort | uniq -c | sort -rn`

## Step 2: Identify External Contributors

To determine if a contributor is external, check for an `@entire.io` email:

```bash git log --all --format='%an <%ae>' --author="<name>" | sort -u ```

If they have an `@entire.io` email anywhere in git history, they are **internal**. Only list external contributors in the Thanks section.

Also check the memory file at `memory/project_team_members.md` for known internal/external mappings.

## Step 3: Write the Entry

Insert the new version section at the top of `CHANGELOG.md`, after the header and before the previous version.

### Format

Follow the existing style in CHANGELOG.md exactly:

```markdown ## [X.Y.Z] - YYYY-MM-DD

### Added

- Feature description with context ([#123](https://github.com/entireio/cli/pull/123))

### Changed

- Change description ([#456](https://github.com/entireio/cli/pull/456))

### Fixed

- Bug fix description ([#789](https://github.com/entireio/cli/pull/789))

### Housekeeping

- Maintenance item ([#101](https://github.com/entireio/cli/pull/101))

### Thanks

Thanks to @contributor for description of contribution! ```

### Style Rules

- **Sections**: Added, Changed, Fixed, Housekeeping, Thanks. Omit empty sections. - **Each bullet**: starts with a dash, concise description, PR link(s) at the end - **Group related PRs** into a single bullet when they're part of the same feature/fix - **Work-in-progress features**: call out explicitly, e.g., "Feature X (work in progress): ..." - **Known limitations**: note inline, e.g., "Note: subagent tracking is not yet supported due to..." - **Thanks section**: only external contributors. Name what they contributed specifically. - **Dependency bumps**: group into a single Housekeeping bullet unless a bump fixes a notable bug - **PR links**: always use full URL format `[#N](https://github.com/entireio/cli/pull/N)` - **No trailing period** on bullet items - **Date**: use the current date in YYYY-MM-DD format

### Categorization Guide

- **Added**: new features, new commands, new agent integrations, new CI workflows - **Changed**: behavior changes, API changes, UX changes, migrations - **Fixed**: bug fixes, E2E fixes, agent-specific fixes - **Housekeeping**: dependency bumps, docs, refactors, CI improvements, test improvements

Intended uses

  • Use Changelog when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.