agentleFS
Sign inStart free
prestariusprestarius/jet-skills-stack/skills/release-notes/SKILL.md

release-notes

Skill1 starsChanged 2 months agoMITView on GitHub

Turn git history since a tag or date into a changelog entry or release notes grouped by change type, in the project's changelog format. Use whenever the user asks for "release notes", "changelog", "what's in this release", "write the CHANGELOG entry", or is tagging a version. For a stakeholder progress update use status-report instead.

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, 1 is distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write release notes from what actually shipped, not from commit messages verbatim.

    line 8
  2. Very specific:

    Pin the range: Default to the last tag to HEAD (git describe --tags --abbrev=0).

    line 10
  3. Very specific:

    Match the house format: Read CONTEXT.md (conventions) and the existing CHANGELOG.md.

    line 15
  4. Very specific:

    Don't invent items; if a commit is unclear, mark it TODO: confirm rather than guessing.

    line 22

“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

Write release notes from what actually shipped, not from commit messages verbatim.

  1. Pin the range. Default to the last tag to HEAD (git describe --tags --abbrev=0); accept a range, tag, or date from $ARGUMENTS. State the range at the top.
  2. Read the changes, not just the log. git log --no-merges --format='%h %s%n%b' <range> plus git diff --stat <range>; open the diff for anything whose commit message is vague. Outcomes, not commits: "Force pushes are now blocked by the guardrail hook", not "update hook".
  3. Match the house format. Read CONTEXT.md (conventions) and the existing CHANGELOG.md; default to Keep a Changelog headings (Added / Changed / Fixed / Removed / Security / Deprecated) and semver. Keep the existing file's voice and heading style.
  4. Flag what the reader must act on. Breaking changes, migrations, config changes, new defaults — first, with the one-line upgrade step. Never bury a breaking change in "Changed".
  5. Cross-link. Issue/PR numbers from the tracker vocabulary in CONTEXT.md; ADRs by number.
  6. Output. The entry as Markdown (or the edited CHANGELOG.md if asked), ready to paste. Don't invent items; if a commit is unclear, mark it TODO: confirm rather than guessing.

Omit "minor fixes and improvements" filler; either name the fix or drop the line.

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