agentleFS
Sign inStart free
MrCipherSmithMrCipherSmith/goodai-base/skills/changelog/SKILL.md

changelog

Skill0 starsChanged 5 months agoMITView on GitHub

Use when generating a changelog, release notes, or summarizing what changed between tags, versions, or date ranges.

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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 149 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Default: from latest tag to HEAD

    line 35
  2. Very specific:

    If gh CLI available: fetch PR titles for merge commits, get authors and labels.

    line 59
  3. Distinctive:

    If no conventional commits found, fall back to plain list by date

    line 82

“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

Changelog Generator

Generate structured changelog from git history.

Arguments

  • /changelog — latest tag to HEAD
  • /changelog v1.0..v2.0 — between tags
  • /changelog --since 2024-01-01 — since date
  • /changelog --output <file> — write to file
  • /changelog --prepend — prepend to existing CHANGELOG.md
  • /changelog --format compact — one-liner per change

Workflow

Step 1: Determine Range

  1. git tag --sort=-version:refname — list recent tags
  2. Default: from latest tag to HEAD
  3. Between tags or since date if specified

Step 2: Collect Commits

git log <range> --pretty=format:"%H|%s|%an|%ad" --date=short

Step 3: Parse & Classify

PrefixSection
feat:Features
fix:Bug Fixes
perf:Performance
refactor:Refactoring
docs:Documentation
test:Tests
chore:Maintenance
BREAKING CHANGEBreaking Changes

Extract scope, PR references (#123), issue references fixes #456.

Step 4: Enrich (optional)

If gh CLI available: fetch PR titles for merge commits, get authors and labels.

Step 5: Generate Output

# Changelog

## [v1.3.0] - 2024-03-15

### Breaking Changes
- **auth**: Remove deprecated OAuth1 support (#234)

### Features
- **api**: Add batch processing endpoint (#220)

### Bug Fixes
- **db**: Fix connection pool leak under load (#228)

Rules

  • Deduplicate identical commit messages
  • Skip merge commits (use PR title instead)
  • If no conventional commits found, fall back to plain list by date
  • Breaking changes always go first
  • One line per change

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