- Home
- Skills
- Frontend & Web Apps
- Component Library Releases: Catch Breaking Changes
Works with the AI Agents you already use
Component Library Releases: Catch Breaking Changes
Point it at a PR or diff and get a release review written for the people who will upgrade.
$6
Component Library Releases: Catch Breaking Changes
Example session with this skill installed
Review this PR in our @acme/ui package (2.4.1, peer react ^18.2.0 || ^19.0.0) before release. Changes to button.tsx: renamed variant destructive to danger, changed default size to sm, replaced forwardRef with ref as a prop, renamed data-slot="button" to "btn", added an optional loading prop.
- Read your context and instructions
- Compiled the component library releases
- Generated the UI component
Release review: @acme/ui 2.4.1 → 3.0.0 (or 2.5.0 with the deprecation plan)
Context: versioned npm package. peerDependencies: react ^18.2.0 || ^19.0.0, tailwindcss ^4. React 18 is still supported, so ref rules for React 18 apply.
Verdict
MAJOR as written, because four changes break existing consumers, two of them without any type error.
Changes
| Change | Level | Why it matters to consumers |
|---|---|---|
Variant destructive renamed to danger | Major | variant="destructive" stops compiling; untyped usages silently fall back to the default style. |
Default size changed from default to sm | Major | Every <Button> without size becomes smaller. No type error. |
forwardRef removed, React 18 still in peer range | Major | On React 18 the ref is null (focus, tooltips, popover anchors break). TypeScript does not catch it. |
data-slot="button" renamed to data-slot="btn" | Major | Consumer selectors like [data-slot=button] stop matching. Visual only. |
New optional loading prop | Minor | Additive. See the issue below. |
Must fix before release
button.tsx:loadingonly setsaria-busy; the button stays clickable, so forms can submit twice. Disable it while loading, or document that consumers must handle it.
Deprecation plan (ships as 2.5.0 instead of 3.0.0)
- Keep both
destructiveanddangerincvawith the same classes; warn once in development builds whendestructiveis used. TypeScript cannot mark a single string-union member as deprecated, so the changelog and the warning carry the message. - Keep
size: "default"as the default. Change it in 3.0.0. - Keep
forwardRefuntil the peer range drops React 18 (3.0.0). - Keep
data-slot="button".
Changelog entry (consumer-facing, 2.5.0)
Added
Button:loadingprop. Setsaria-busyand disables the button while true.Button:dangervariant.
Deprecated
Button:variant="destructive". Usevariant="danger". Removed in 3.0.0.
Migration notes (for 3.0.0)
variant="destructive"→variant="danger".- If you relied on the default size, pass
size="default"explicitly before upgrading. - Requires React 19.
- Search your styles for
[data-slot=button]if the slot rename ships.
button.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
For teams that maintain a component library other apps depend on (shadcn/ui-style, Tailwind, Radix or Base UI). Point it at a PR or diff and get a release review written for the people who will upgrade.
Why this exists
The official shadcn skill helps an app use components. This one helps you maintain a library others consume, where the question is "what happens to every app that upgrades?". Use them together.
What it catches
- Silent breaks TypeScript misses: dropping
forwardRefwhile React 18 is still in your peer range (refs becomenull), renameddata-slotvalues, CSS variable renames or HSL to OKLCH format changes, changed default props. - Classic breaks: removed or renamed exports, props and variant values, narrowed prop types, new required peers.
- Subtle minors: a new variant can still break consumers who use exhaustive
Record<Variant, ...>maps. - API quality on touched components:
classNamemerging, prop spreading, ref target,asChild, controlled/uncontrolled naming,cvavariants, tokens instead of hardcoded colors.
What you get
A recommended version bump with the main reason, a change-by-change table, must-fix issues with minimal code fixes, a deprecation plan that often turns a major into a minor, a consumer-facing changelog entry and migration notes.
Notes
- Works for versioned packages and for copy-in (shadcn-style) registries.
- Read-only: it may run
git diff,git logorgit showto read the change, and never commits or writes files. You can also paste a diff. - It only classifies what is in the diff and says "breaking if consumers do X" when it cannot see consumer code.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Does not run your tests or visual regression suite. Cannot see how consumer apps use the library: when a change is breaking only for some usage, it says so and suggests what to search for. Not a replacement for the official shadcn skill for building components.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Nothing to install. It runs in your AI agent.
- Optional
Git (to read diffs)
Permissions
File Scopes
Read-only. Reads library source and config. May run read-only git commands (git diff, git log, git show) to get the change. Never commits, checks out or writes files. No network access.