breaking-changes

Solid

Detect breaking changes in Claude Code updates by comparing current API surface against changelog. Maps impacts to specific plugin files. Use when: checking whether a Claude Code update breaks our plugin ecosystem (hooks, agent frontmatter, manifest schema, or skill format).

API & Backend 22 stars 3 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Breaking Changes Detection Skill ## Overview Compares Claude Code API changes against our plugin ecosystem to detect compatibility issues. ## API Surface File The `api-surface.md` reference contains our current known API: - Hook types and their matchers - Agent frontmatter fields - Plugin manifest schema - Skill SKILL.md format - Script CLI flags used ## Detection Workflow 1. **Load** current api-surface.md 2. **Fetch** latest Claude Code API docs 3. **Diff** for added/changed/removed APIs 4. **Grep** our plugins for each changed API 5. **Report** with file:line impact mapping ## Impact Assessment | Change Type | Severity | Example | |-------------|----------|---------| | Removed API | BREAKING | Hook type deleted | | Changed schema | BREAKING | Frontmatter field renamed | | New required field | BREAKING | Mandatory new param | | Deprecated API | DEPRECATED | Old hook still works | | New optional API | NEW | New hook type added | ## References - [API Surface](references/api-surface.md) - [Migration Guide Template](references/templates/migration-guide.md)

Details

Author: fusengine
Repository: fusengine/agents
Created: 6 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

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.

0 Updated 1 weeks ago

windchillscalanthes-ship-it

AI & Automation Listed

code-breaking-changes

Breaking changes

468 Updated 1 weeks ago

deonmenezes

Data & Documents Solid

changelog-scan

Scan Claude Code changelog for new versions, features, and changes. Fetches official docs, parses release notes, and generates structured update report. Use when: checking for new Claude Code versions, features, or changes since the last known release.

22 Updated 2 days ago

fusengine