api-changelog-automation SKILL.md skillA
api-changelog-automation from samber/developer-platform-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-platform-skills/api-changelog-automation@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-platform-skills
- Path
skills/api-changelog-automation/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.1, committed Oct 25, 2026
- First version recorded
- Oct 25, 2026
- Size
- 21,283 bytes
- Repository stars
- 9
- License
- MIT
Designs the provider-side pipeline that turns contract diffs of an API you publish (OpenAPI, GraphQL SDL, protobuf, AsyncAPI) into a breaking-change CI gate and a traced, per-version API changelog feed, classified by your own policy. Use whenever the user mentions oasdiff, openapi-diff, graphql-inspector diff, buf breaking, API schema checks, failing a PR on breaking changes to a published API contract, or an auto-generated API changelog. Do NOT use for release-note prose…
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
# API Changelog Automation You are building the machinery that notices every change to a published API contract, decides whether it breaks callers by your own written rules, stops the unapproved breaks, and writes a record integrators and their tools can read. The deliverable is a pipeline design: severity map, baselines, CI gate, declared-change channel, approval record, entry schema and feed, each wired to a file in the repo. The recurring failure is trusting the diff tool twice: once for what counts as breaking (its defaults are not your policy) and once for what changed at all (it only sees declared structure). A green check then publishes a changelog that omits the change that broke a partner. Boundaries: - The breaking-change definition, notice windows and sunset rules come from `samber/developer-platform-skills@api-versioning-policy`. This skill encodes that policy into tool configuration; it never invents one. - Polishing entries into readable release notes belongs to `samber/developer-relations-skills@changelog-writing`; the before/after upgrade guide to `samber/developer-relations-skills@version-migration-guide`. This skill hands them traced, structured entries. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-platform-skills/api-changelog-automation@sha256:87fd7eaaeca1fd05The line at the top of this page pins the label v1.0.1, 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_opnbev43gwgtzmum)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 25, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-10-25 | 4e87402 | 21,283 B | A | view · diff |
| v1.0.0 | 2026-10-25 | c2af680 | 21,234 B | A | view |
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 (21283 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
samber/developer-platform-skills · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_opnbev43gwgtzmum GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-platform-skills/api-changelog-automation GET https://markdownregistry.com/api/v1/blob/87fd7eaaeca1fd054f344350d82d39ae3d42cb9dc7db80d1730645cfaa989e37
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.