agentleFS
Sign inStart free
jelbirtjelbirt/LLM-Skill-Build/release-notes/SKILL.md

release-notes

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Generate release notes from git history since the last tag, grouped into features, fixes, breaking changes, and improvements using conventional-commit prefixes. Use when the user wants release notes, a changelog, or a summary of what shipped since the last release - works directly from raw commit history, so it fits direct-to-main workflows or repos that don't rely on GitHub's PR-label-based release notes generator.

176 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, brainstorm-ideas-new 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.
  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 6 projects that use this

  • skytiger6724Skill

    brainstorm-ideas-new

    Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.

    Also in 6 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 6 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 6 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 6 projects that use this

  • +7 more from skytiger6724

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 162 edited versions we read keep these.

  • 1

    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:

    Write user-friendly descriptions (not raw commit messages)

    line 25

“Common” is measured: kept by at least 6 in 10 of the 162 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

Context

  • Last tag: !git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"
  • Commits since last tag: !git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~20)..HEAD --oneline
  • Changed files: !git diff --stat $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~20)..HEAD

Task

Generate release notes from the commits above. Follow these steps:

  1. Group commits by type using conventional commit prefixes or inferred categories:
    • Features — New functionality
    • Fixes — Bug fixes
    • Breaking Changes — Anything that breaks backwards compatibility (highlight prominently)
    • Improvements — Refactoring, performance, DX improvements
    • Documentation — Doc changes
    • Other — Everything else
  2. Write user-friendly descriptions (not raw commit messages)
  3. Omit empty categories
  4. Format as markdown with this structure:
# Release Notes — [version or date]

## Breaking Changes
- Description of breaking change

## Features
- Description of feature

## Fixes
- Description of fix

## Improvements
- Description of improvement

Output only the formatted release notes.

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