breaking-change-detection SKILL.md skillA
breaking-change-detection from sigistry/marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sigistry/marketplace/breaking-change-detection@git:20260826.571bc2fPins git:20260826.571bc2f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sigistry/marketplace
- Path
plugins/release-conductor/skills/breaking-change-detection/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260826.571bc2f, committed Aug 26, 2026
- First version recorded
- Jul 8, 2026
- Size
- 3,782 bytes
- Repository stars
- 3
- License
- MIT
This skill should be used when the user mentions "breaking change", "semver", "semantic versioning", "major minor patch", "version bump", "backward compatible", "API compatibility", or "deprecation". Provides a decision matrix and per-ecosystem signals for reasoning about behavioral (not just syntactic) breaking changes.
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 Change Detection ## Purpose Standardize how a change is classified against Semantic Versioning by reasoning about its effect on *consumers*, including behavioral breaks that leave the syntax intact. Humans get binary compatibility right only about 60% of the time; this methodology closes the gap with an explicit decision matrix and per-ecosystem catalogs. Tech-agnostic. ## First: is the change on the public surface? Only changes to the **public API surface** can be breaking or minor. Establish the surface before classifying (detailed per ecosystem in `references/breaking-change-catalog.md`): | Ecosystem | Public surface | |-----------|----------------| | JS/TS | `package.json` `exports`/`main`, named/default exports, `.d.ts` | | Python | `__all__`, non-`_` names, entry points | | Go | Capitalized identifiers outside `internal/` | | Java/C# | `public`/`protected` members of exported packages | | Rust | `pub` items reachable from the crate root | | CLI | flags, subcommands, arg order, exit codes, stdout format | | HTTP | routes, methods, request/response schema, status codes | | GraphQL | types, fields, args, nullability, enum values | …
Read the whole file at its exact version.
How to install
mdr add sigistry/marketplace/breaking-change-detection@sha256:94b4f13ccd8371a4The line at the top of this page pins the label git:20260826.571bc2f, 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_p266ibebuo5jcmmy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 8, 2026 and Aug 26, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.571bc2f latest | 2026-08-26 | 571bc2f | 3,782 B | A | view · diff |
| git:20260715.fcd8714 | 2026-07-15 | fcd8714 | 3,782 B | A | view · diff |
| git:20260708.c0884a9 | 2026-07-08 | c0884a9 | 3,791 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 (3782 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
sigistry/marketplace · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p266ibebuo5jcmmy GET https://markdownregistry.com/api/v1/resolve?ref=sigistry/marketplace/breaking-change-detection GET https://markdownregistry.com/api/v1/blob/94b4f13ccd8371a4395e45bee1c0a60f44a845067bfd0a25ccee5cfd5816b6a5
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.