agentleFS
Sign inStart free
viknesh20-20viknesh20-20/claude-code-tool-kit/.claude/skills/changelog/SKILL.md

changelog

Skill7 starsChanged 7 months agoMITView on GitHub

Generates a changelog from git history following Keep a Changelog format. Categorizes commits into Added, Changed, Fixed, Removed, Security, and Breaking Changes. Use before releases or to document recent work.

160 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, soak-test and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 12 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 14 projects that use this

  • +5 more from lilangMax
  • +3 more from CoralGame

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 149 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    If a tag/ref is provided, use: git log <tag>..HEAD

    line 24
  2. Distinctive:

    If "last-release" is specified, find the most recent tag

    line 25
  3. Distinctive:

    If "unreleased" or no argument, show all commits since last tag

    line 26
  4. Distinctive:

    If a CHANGELOG.md exists, prepend the new section

    line 85
  5. Distinctive:

    If not, create a new CHANGELOG.md

    line 86
  6. Distinctive:

    Always show the generated content for review before saving

    line 87
  7. Distinctive:

    Follow Keep a Changelog format exactly

    line 92
  8. Distinctive:

    Don't include merge commits

    line 94
  9. Distinctive:

    Don't include chore/ci-only commits unless significant

    line 95

“Common” is measured: kept by at least 6 in 10 of the 149 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate Changelog

Git History

!git log --oneline --no-merges -50 2>/dev/null

Tags

!git tag --sort=-v:refname 2>/dev/null | head -10

Latest Tag

!git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"

Instructions

Step 1: Determine Range

  • If a tag/ref is provided, use: git log <tag>..HEAD
  • If "last-release" is specified, find the most recent tag
  • If "unreleased" or no argument, show all commits since last tag

Step 2: Gather Commits

Run: git log <range> --oneline --no-merges

For each commit, extract:

  • Commit hash (short)
  • Commit message
  • Author
  • Date
  • PR number (if referenced)

Step 3: Categorize

Group commits using Keep a Changelog categories:

  • Added: New features, endpoints, commands, pages
  • Changed: Modifications to existing functionality, API changes
  • Fixed: Bug fixes, error corrections
  • Deprecated: Features marked for removal
  • Removed: Deleted features, removed dependencies
  • Security: Vulnerability fixes, security improvements
  • Breaking Changes: Changes that require consumer updates

Detection heuristics:

  • feat: / feature: / add: → Added
  • fix: / bugfix: / hotfix: → Fixed
  • refactor: / update: / change: → Changed
  • remove: / delete: / drop: → Removed
  • security: / vuln: / cve: → Security
  • BREAKING: / BREAKING CHANGE: → Breaking Changes
  • Other: categorize by reading the commit message

Step 4: Format Output

# Changelog

## [Unreleased] — YYYY-MM-DD

### Added
- Description of new feature (#PR)

### Changed
- Description of change (#PR)

### Fixed
- Description of fix (#PR)

### Removed
- Description of removal (#PR)

### Security
- Description of security fix (#PR)

### Breaking Changes
- Description of breaking change (#PR)

Step 5: Save or Display

  • If a CHANGELOG.md exists, prepend the new section
  • If not, create a new CHANGELOG.md
  • Always show the generated content for review before saving

Rules

  • Follow Keep a Changelog format exactly
  • Include PR/issue references where available
  • Don't include merge commits
  • Don't include chore/ci-only commits unless significant
  • Group related commits into single entries where appropriate

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free