release-notes-draft SKILL.md skillA
release-notes-draft from product-on-purpose/agent-skills-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/agent-skills-toolkit/release-notes-draft@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/agent-skills-toolkit
- Path
tests/fixtures/audit-corpus-labelled/02-excellent-orphan/skills/release-notes-draft/SKILL.md- Versions recorded
- 1
- Latest version
- v0.1.0, committed Nov 1, 2026
- Size
- 1,629 bytes
- Repository stars
- 3
- License
- Apache-2.0
Drafts user-facing release notes from the commits between two git refs, grouping by feature, fix, and breaking change, and flagging anything that needs a migration note. Use when the user asks for release notes, a changelog entry, or a summary of what changed between two tags or since the last release.
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 ## Purpose Turn a commit range into release notes a user can read: what is new, what is fixed, what breaks, and what they must do about it. ## Procedure 1. Establish the range. Default: the last tag to `HEAD` (`git describe --tags --abbrev=0`). If the user names two refs, use those. 2. List commits with `git log --no-merges --format='%h%x09%s%x09%b' <range>`. Group by conventional-commit type if present (feat, fix, perf, docs, refactor, chore); otherwise infer from the subject and say the grouping is inferred. 3. For each `feat` and `fix`, write one user-facing sentence: what changed for someone using the software, not what the code did. Drop internal-only chores unless the user asks for a full changelog. 4. Breaking changes: anything with `!` in the subject, a `BREAKING CHANGE:` footer, a removed CLI flag, a renamed public function, or a changed default. Each one gets a "what to do" line. 5. Link each bullet to its commit or PR when a remote is configured. ## Output shape ``` ## <version> - <date> ### Breaking ### Added ### Fixed ### Upgrade notes ``` …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/agent-skills-toolkit/release-notes-draft@sha256:f026f671f91febb1The line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4sn27csovgos7mvz)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 1, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1629 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/agent-skills-toolkit · 3 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4sn27csovgos7mvz GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/agent-skills-toolkit/release-notes-draft GET https://markdownregistry.com/api/v1/blob/f026f671f91febb1f92fb403a35a5b5b0cec9ee65373ea20e4037560783b68c5
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.