breaking-changes
SolidUse when checking whether a Claude Code update breaks our plugin ecosystem — hooks, agent frontmatter, manifest schema, or skill format.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- fusengine
- Repository
- fusengine/agents
- Created
- 8 months ago
- Last Updated
- 6 days ago
- Language
- CSS
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
breaking-change-detector
Compares two versions of a codebase or API and flags all breaking changes with migration hints.
breaking-change-detection
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.
api-break-check
Review an API change for backward-incompatible breaking changes before it ships and breaks existing consumers — removed or renamed fields, added required request parameters, narrowed types, tightened validation, changed status codes or error shapes, removed enum values, and (for gRPC) changed field numbers. Explains who breaks and why, then rewrites the change to be compatible: additive evolution, deprecate-then-sunset, or a new version with expand/contract. Use whenever writing, reviewing, or about to merge a change to an API contract — an OpenAPI / Swagger spec, a GraphQL schema, a protobuf / gRPC definition, or the handlers/DTOs/serializers behind them — especially for an API with consumers you don't control.