changelog SKILL.md skillA
changelog from jorgecostamacia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jorgecostamacia/skills/changelog@git:20261116.2cacb7dPins git:20261116.2cacb7d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jorgecostamacia/skills
- Path
plugins/changelog/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261116.2cacb7d, committed Nov 16, 2026
- First version recorded
- Nov 9, 2026
- Size
- 4,155 bytes
- Repository stars
- 2
- License
- MIT
How a repository keeps its changelog: one CHANGELOG.md at the root listing, newest first, only what whoever consumes the repo has to act on. Use when cutting a release, bumping a major, changing a default, a requirement or a name a consumer depends on, deciding whether a change needs an entry, or when a README or AGENTS file starts to accumulate version history ("since 3.0…", "4.0.0 moved…"). It encodes what goes in and what stays out, the format, that the entry is written on the 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
# Changelog — what a consumer has to act on A repository that others consume — a library, a published contract, a read model, an API — keeps **one `CHANGELOG.md` at its root**. It answers one question for whoever upgrades: *what do I have to do?* Everything else about a version is already in git: the commits and the tag. The version's section is also its Release's notes on the forge, so whoever reads the Release reads the same text. ## What goes in - **Every major**: what breaks and what to do about it — the renamed id, the moved topic or route, the removed field. A major that changes nothing a consumer compiles against (new topics, a new store schema) gets its entry all the more: it is the one that looks safe and is not. - **A behavior change in a minor**: a new default, a renamed log message or metric someone may query or alert on, a new requirement on the environment (a schema migration, a runtime version), a deprecation. - **A first release that continues something published elsewhere** (other package ids, another transport, another repository): where the old one went and how to move. ## What stays out …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ymbpbi7ui5esvoa6/6afccfa29e8989a2ca5eb19e3a2ca16591ad22e5f46bb6f0362fd792cfee3329.json
Then /plugin install changelog@markdownregistry-ymbpbi7ui5esvoa6 in Claude Code. It installs git:20261116.2cacb7d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jorgecostamacia/skills/changelog@sha256:6afccfa29e8989a2The line at the top of this page pins the label git:20261116.2cacb7d, 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_ymbpbi7ui5esvoa6)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in jorgecostamacia/skills/changelog since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of changelog from somewhere else? Ask it: where did my changelog come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Nov 9, 2026 and Nov 16, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.2cacb7d latest | 2026-11-16 | 2cacb7d | 4,155 B | A | view · diff |
| git:20261116.f4b30a3 | 2026-11-16 | f4b30a3 | 4,108 B | A | view · diff |
| git:20261109.86064cf | 2026-11-09 | 86064cf | 3,837 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/changelog/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (4155 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
jorgecostamacia/skills · 2 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ymbpbi7ui5esvoa6 GET https://markdownregistry.com/api/v1/resolve?ref=jorgecostamacia/skills/changelog GET https://markdownregistry.com/api/v1/blob/6afccfa29e8989a2ca5eb19e3a2ca16591ad22e5f46bb6f0362fd792cfee3329
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 jorgecostamacia/skills
Every file in jorgecostamacia/skills