changelog SKILL.md skillA
changelog from vivantel/kms is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vivantel/kms/changelog@git:20260829.47ff630Pins git:20260829.47ff630 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vivantel/kms
- Path
plugins/kms/skills/changelog/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260829.47ff630, committed Aug 29, 2026
- Size
- 1,726 bytes
- Repository stars
- 3
- License
- MIT
Generate a CHANGELOG.md entry from git commit history (since the last tag, or full history if none exists), grouped Keep a Changelog style from Conventional Commit type prefixes and Why-bodies. Use when the user wants a changelog produced or updated, e.g. "generate a changelog", "update the changelog for this 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
Generate a `CHANGELOG.md` entry from git commit history. This skill only runs when explicitly invoked — never automatically. ## Determining the commit range 1. Find the most recent tag with `git tag --list` (or `git describe --tags --abbrev=0`). 2. If a tag exists, use `git log <tag>..HEAD`. 3. If no tag exists, use the full history (`git log`). ## Rendering entries 1. For each commit in range, parse the Conventional Commit type prefix from the summary line and the Why-body from the message. 2. Map type to category: - `feat` → **Added** - `fix` → **Fixed** - `docs` → **Documentation** - `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore` → **Changed** 3. Under each category heading, list one bullet per commit using its Why-summary — not its raw Conventional Commits subject line. 4. Ask the user for a version number and date before writing anything. Write the section heading as `## [x.y.z] - date`. Never write to or invent an `[Unreleased]` section, and never infer the version number yourself. ## Output Prepend the new section to `CHANGELOG.md` at the repo root. If the file doesn't exist yet, create it with a top-level `# Changelog` heading. …
Read the whole file at its exact version.
How to install
mdr add vivantel/kms/changelog@sha256:8e2c673184e0aa87The line at the top of this page pins the label git:20260829.47ff630, 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_3ihaka26mr2gg2mu)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 29, 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 (1726 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
vivantel/kms · 3 stars · license MIT · pushed 2026-10-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_3ihaka26mr2gg2mu GET https://markdownregistry.com/api/v1/resolve?ref=vivantel/kms/changelog GET https://markdownregistry.com/api/v1/blob/8e2c673184e0aa875db31c764b8271aa727d7e8bdd41f1336241900408df0a50
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.