library-release-checker

Identify breaking changes and deprecations from library release notes.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/snhrm/claude-plugin --skill library-release-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-release-checker
Source: https://github.com/snhrm/claude-plugin/tree/main/plugin/skills/library-release-checker
Command: npx skills add https://github.com/snhrm/claude-plugin --skill library-release-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fetches release information from GitHub and official docs to identify breaking changes, deprecations, and built-ins, enabling safe upgrades.

Core Features & Use Cases

  • Breaking Changes: Detects major API changes that may impact downstream code.
  • Deprecations: Identifies deprecated APIs and suggested alternates.
  • Built-ins: Flags APIs that have been bundled or inlined in newer versions.
  • Migration Guides: Provides direct links to upgrade instructions.

Quick Start

Retrieve release notes for library 'react' from its official blog and migration guide to plan a safe upgrade path.

Frequently Asked Questions about library-release-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify breaking changes when upgrading a library?

Breaking changes are major API modifications that impact downstream code. This Skill fetches release notes from GitHub and official documentation to automatically detect breaking changes, deprecations, and migration guidance, enabling you to assess upgrade safety before proceeding.

Can I detect deprecations across multiple library versions?

Yes. The Skill parses release notes and migration guides to identify deprecated APIs and their suggested replacements across version histories, surfacing which features are no longer recommended and what to use instead.

What sources does this tool check for release information?

The Skill retrieves data from GitHub releases, official changelogs, and migration guides published by library maintainers, aggregating breaking changes, deprecations, and built-ins from these sources into structured JSON output.

How do I plan a safe upgrade path for my dependencies?

Extract release notes for your target version to review breaking changes, deprecations, and built-ins, then use the migration guidance and direct links provided to execute the upgrade systematically and validate compatibility.

What happens when a library bundles or inlines APIs in newer versions?

Built-ins—APIs bundled or inlined in newer versions—are flagged by the Skill so you can identify which external dependencies became unnecessary and remove them from your dependency tree during upgrade.