agentleFS
Sign inStart free
shyamw-cloudshyamw-cloud/Claude-skill/.claude/skills/release-notes/SKILL.md

release-notes

Skill0 starsChanged 7 months agoMITView on GitHub

Use to turn a list of merged PRs (or a git log range) into customer-facing release notes. Groups by theme, leads with what changed for the user (not what was refactored), and produces both a long form and a 3-bullet TL;DR.

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

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 162 edited versions we read keep these.

  • 4

    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:

    Never include "refactored X" or "improved code quality" in customer notes.

    line 55
  2. Distinctive:

    Never list a fix that wasn't a customer-visible bug.

    line 56
  3. Distinctive:

    Never use version numbers as headers ("v2.4.1") without a name or theme alongside.

    line 57
  4. Distinctive:

    Always include a "Fixes & quality" section, even if short — it builds trust.

    line 58

“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

release-notes

Engineering changelogs and customer release notes are different things. This skill produces the customer version: focused on what is now possible, not what files were touched.

Inputs to gather

  • Range — git tag, PR list, or date range.
  • Audience — end users, admins, developers integrating the API?
  • Tone — punchy product-update or formal enterprise note?

Method

  1. Pull the PR list / commits.
  2. Drop everything that doesn't change observable behavior (refactors, deps bumps, internal docs).
  3. Cluster the rest into 3-5 themes (e.g. "Faster onboarding", "Better search", "More reliable webhooks").
  4. For each item: write one line on what's new, and one line on why the user should care.
  5. Lead with the biggest user-visible win.

Output format

## TL;DR (3 bullets)
- <biggest win>
- <second biggest>
- <one notable fix or quality-of-life change>

## What's new

### <Theme 1>
- **<feature>** — <what's new>. <why you should care>
- **<feature>** — <what's new>. <why you should care>

### <Theme 2>
- ...

## Fixes & quality
- <fix> — <user-visible impact>
- <fix> — <user-visible impact>

## For developers (only if API/SDK changed)
- <breaking change>: <migration steps>
- <new endpoint>: <one-line description>

## Coming next (optional)
- <one teaser; only include if marketing approved>

Hard rules

  • Never include "refactored X" or "improved code quality" in customer notes.
  • Never list a fix that wasn't a customer-visible bug.
  • Never use version numbers as headers ("v2.4.1") without a name or theme alongside.
  • Always include a "Fixes & quality" section, even if short — it builds trust.

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