What problem does it solve? Upgrading dependencies, language versions, or frameworks requires manually reading changelogs, hunting down deprecated API usage across a codebase, and tracking breaking changes, which is error-prone and time-consuming. ## Core Features & Use Cases - Breaking Change Detection: Identifies removed functions, changed signatures, and deprecations between two versions of a package, language, or framework. - Affected Code Search: Greps the codebase for usage of deprecated or removed APIs and lists exact file locations to update. - Structured Migration Report: Produces a step-by-step migration plan with before/after code examples, checklists, and verification commands. - Use Case: When upgrading Django from 4.0 to 5.0, invoke the skill to get a report of breaking changes, the files in your project that use affected APIs, and an ordered checklist of fixes with test verification steps. ## Quick Start Ask Claude to migrate the requests dependency from version 2.28 to 2.31 and generate a migration report for the current codebase.