breaking-changes-management SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
breaking-changes-management from practicalswan/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add practicalswan/agent-skills/breaking-changes-management@v2.0Pins v2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- practicalswan/agent-skills
- Path
breaking-changes-management/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0, committed Sep 7, 2026
- First version recorded
- Aug 24, 2026
- Size
- 4,787 bytes
- Repository stars
- 24
- License
- MIT
Manage breaking API changes, migration guides, deprecation notices, and semver versioning. Use when introducing breaking changes, writing migration paths, updating changelogs, or releasing major versions.
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
# Breaking Changes Management Use this skill when behavior, interfaces, configuration, or compatibility contracts change in a way that can break consumers. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Activation Conditions Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. - Releasing a major version - Renaming or removing public APIs - Changing request or response shapes - Replacing config keys, env vars, CLI flags, or file formats - Writing migration notes, deprecation notices, or upgrade checklists ## Workflow 1. Identify the exact consumer-visible break. 2. State who is affected and from which version. 3. Provide the replacement path or mitigation. 4. Add before/after examples. 5. Update `CHANGELOG.md` and any setup or usage docs that changed. ## Required Outputs - Changelog entry with a clear `BREAKING` label - Migration guide with old usage, new usage, and upgrade steps - Deprecation timeline if removal is delayed - Validation notes for any examples or scripts that changed <!-- MCP:START --> <!-- PORTABILITY:START --> ## Cross-Client Portability …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_u4rijve4o6errbzo/75005f199c85c9241d06222967695f94c6ba11627f33608040ec79d728c82390.json
Then /plugin install breaking-changes-management@markdownregistry-u4rijve4o6errbzo in Claude Code. It installs v2.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add practicalswan/agent-skills/breaking-changes-management@sha256:75005f199c85c924The line at the top of this page pins the label v2.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_u4rijve4o6errbzo)
1 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 practicalswan/agent-skills/breaking-changes-management 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 breaking-changes-management from somewhere else? Ask it: where did my breaking-changes-management 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 5 versions of this file, between Aug 24, 2026 and Sep 7, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.0 latest | 2026-09-07 | afbb609 | 4,787 B | A | view · diff |
| v2.0 | 2026-09-05 | da1f686 | 4,917 B | A | view · diff |
| v2.0 | 2026-08-31 | 4069d99 | 4,917 B | A | view · diff |
| v2.0 | 2026-08-29 | f108298 | 4,917 B | A | view · diff |
| v2.0 | 2026-08-24 | 4d12f29 | 4,917 B | A | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds the newest version.
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
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/breaking-changes-management/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 (4787 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
practicalswan/agent-skills · 24 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u4rijve4o6errbzo GET https://markdownregistry.com/api/v1/resolve?ref=practicalswan/agent-skills/breaking-changes-management GET https://markdownregistry.com/api/v1/blob/75005f199c85c9241d06222967695f94c6ba11627f33608040ec79d728c82390
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 practicalswan/agent-skills
Every file in practicalswan/agent-skills