agentleFS
Sign inStart free
suxiao1824308603suxiao1824308603/Qoder-devtools-skills/skills/changelog-generator/SKILL.md

changelog-generator

Skill3 starsChanged 9 months agoMITView on GitHub

Generate and maintain CHANGELOG.md files following Keep a Changelog format. Use when the user wants to create a changelog, update release notes, or document version changes.

99 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-test-suite-builder, fda-consultant-specialist 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.
  • Arnav-0Skill

    api-test-suite-builder

    Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    Also in 7 projects that use this

  • Hussain-ElfalahSkill

    fda-consultant-specialist

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 5 projects that use this

  • Hussain-ElfalahSkill

    quality-manager-qmr

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    self-eval

    Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.

    Also in 6 projects that use this

  • ComposioHQSkill

    meeting-notes-and-actions

    Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.

    Also in 4 projects that use this

  • +4 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 93 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this exact structure:

    line 12
  2. Very specific:

    Run git log --oneline <last-tag>..HEAD to get commits since last release

    line 53
  3. Distinctive:

    Write user-facing descriptions (not commit messages)

    line 55
  4. Distinctive:

    Add version header with date

    line 56
  5. Distinctive:

    Update comparison links at bottom

    line 57
  6. Distinctive:

    Write for end users, not developers

    line 72
  7. Distinctive:

    Use present tense ("Add" not "Added")

    line 73
  8. Very specific:

    Keep [Unreleased] section for ongoing work

    line 76
  9. Distinctive:

    Remove empty sections before release

    line 77

“Common” is measured: kept by at least 6 in 10 of the 93 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 changelogs following Keep a Changelog format.

Output Template

Use this exact structure:

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/),
and this project adheres to [Semantic Versioning](https://semver.org/).

## [Unreleased]

### Added
- New features

### Changed
- Changes in existing functionality

### Deprecated
- Soon-to-be removed features

### Removed
- Removed features

### Fixed
- Bug fixes

### Security
- Vulnerability fixes

## [1.0.0] - YYYY-MM-DD

### Added
- Initial release features

[Unreleased]: https://github.com/user/repo/compare/v1.0.0...HEAD
[1.0.0]: https://github.com/user/repo/releases/tag/v1.0.0

Workflow

  1. Run git log --oneline <last-tag>..HEAD to get commits since last release
  2. Categorize commits into Added/Changed/Fixed/etc.
  3. Write user-facing descriptions (not commit messages)
  4. Add version header with date
  5. Update comparison links at bottom

Section Guidelines

SectionContent
AddedNew features for the user
ChangedChanges in existing functionality
DeprecatedFeatures to be removed in future
RemovedFeatures removed in this release
FixedBug fixes
SecuritySecurity vulnerability patches

Rules

  • Write for end users, not developers
  • Use present tense ("Add" not "Added")
  • Group related changes together
  • Most recent version at top
  • Keep [Unreleased] section for ongoing work
  • Remove empty sections before release

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