agentleFS
Sign inStart free
leaf76leaf76/agent-skills/changelog/SKILL.md

changelog

Skill0 starsChanged 3 months agoMITView on GitHub

Generate changelog from git commits. Supports version releases and date ranges. Use when preparing releases, documenting changes, or reviewing commit history for documentation purposes.

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

2 rules. 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no argument, generate changelog for unreleased changes (since last tag or last 2 weeks).

    line 24
  2. Distinctive:

    If commit messages are unclear, read the diff to understand the change

    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

Changelog Generator

You are a technical writer generating clear, user-friendly changelogs from git history.

Step 1: Determine Scope

Check available context:

Latest tags: !`git tag --sort=-version:refname | head -5 2>/dev/null || echo "No tags found"`

If $ARGUMENTS provided:

  • v1.2.0 - changes since that tag
  • v1.1.0..v1.2.0 - changes between tags
  • 7d or 7 days - last 7 days
  • 2024-01-01 - since that date

If no argument, generate changelog for unreleased changes (since last tag or last 2 weeks).

Step 2: Gather Commits

# Since last tag
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~50")..HEAD --oneline

# Or with full details
git log --pretty=format:"%h|%s|%an|%ad" --date=short

Step 3: Categorize Changes

Group commits by conventional commit type:

PrefixCategoryDescription
featNew FeaturesNew functionality
fixBug FixesBug corrections
perfPerformancePerformance improvements
refactorRefactoringCode restructuring
docsDocumentationDoc updates
testTestsTest additions/fixes
choreMaintenanceBuild, deps, config

Output Format

Generate in Traditional Chinese:

# Changelog

## [Unreleased] - YYYY-MM-DD

### New Features
- **feature-name**: Description of what was added (#PR)
- **another-feature**: Description (#PR)

### Bug Fixes
- **component**: Fixed issue where X happened when Y (#PR)

### Performance
- **api**: Reduced response time by X% (#PR)

### Refactoring
- **module**: Restructured X for better maintainability

### Documentation
- Updated README with new setup instructions

### Maintenance
- Upgraded dependency X to version Y
- Fixed CI pipeline configuration

---

### Contributors
- @contributor1
- @contributor2

### Full Changelog
https://github.com/org/repo/compare/v1.0.0...v1.1.0

Guidelines

  • User-focused - describe impact, not implementation details
  • Concise - one line per change, expand only if complex
  • Grouped - combine related small commits into one entry
  • Skip noise - omit merge commits, typo fixes, WIP commits
  • If commit messages are unclear, read the diff to understand the change
  • Include PR/issue numbers when available
  • For breaking changes, add BREAKING prefix

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