release-notes SKILL.md skillA

release-notes from foyzulkarim/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add foyzulkarim/skills/release-notes@git:20260724.cdb1a53

Pins git:20260724.cdb1a53 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

foyzulkarim/skills

Path

dev-pipeline/skills/release-notes/SKILL.md

Versions recorded

1

Latest version

git:20260724.cdb1a53, committed Jul 24, 2026

Size

3,680 bytes

Repository stars

43

License

none declared

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Release Notes

Draft a release changelog by summarizing the commits since the last release, then suggest the
next semver version and prepend the entry to `CHANGELOG.md` at the project root.

## Steps

1. **Find the commit range and version baseline.** Determine the last released tag:

   ```bash
   git describe --tags --abbrev=0 2>/dev/null
   ```

   - If a tag exists, the range is `<tag>..HEAD`, and the tag itself is the version baseline.
   - If no tag exists (fresh repo), use the full history and **ask the developer** for the
     current version — do not infer it from any manifest, lockfile, or config file belonging to
     the project. This skill only reads git; it never inspects a project's toolchain.

2. **Collect the commits** in the range:

   ```bash
   # with a tag:
   git log <tag>..HEAD --oneline --no-merges
   # without a tag:
   git log --oneline --no-merges
   ```

3. **Group the commits** by type, inferring the type from the message
   (Conventional Commits prefix if present, otherwise from the wording):
   - **Features** — new functionality (`feat`, "Add", "Support")
   - **Fixes** — bug fixes (`fix`, "Fix", "Correct")
…

Read the whole file at its exact version.

How to install

mdr add foyzulkarim/skills/release-notes@sha256:0a529ff364854bf8

[![mdr](https://markdownregistry.com/badge/art_oaciq3twejemjxph.svg)](https://markdownregistry.com/a/art_oaciq3twejemjxph)

Versions

The registry has recorded 1 version of this file, committed on Jul 24, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_oaciq3twejemjxph
GET https://markdownregistry.com/api/v1/resolve?ref=foyzulkarim/skills/release-notes
GET https://markdownregistry.com/api/v1/blob/0a529ff364854bf8cd5d9b83a90c11db54ee73c660853bd78d3824b53083ef12

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from foyzulkarim/skills

Every file in foyzulkarim/skills

Other files named release-notes

Browse by kind, by grade A, or by owner.