package-upgrade

Package upgrade planning starts by scanning your package.json to inventory current versions against latest releases. This Skill analyzes your dependencies, fetches the newest versions available, and flags packages that are behind, showing you the version gap and upgrade opportunities across npm, Yarn, or PNPM projects.

Breaking changes are incompatible modifications in new package versions that can crash or alter your code's behavior. This Skill compiles breaking changes for each outdated dependency, researches migration guides, and assesses upgrade risk so you understand what code rewrites or configuration adjustments each upgrade requires.

Safe upgrades require staged planning—prioritizing low-risk updates, grouping related dependencies, and sequencing changes to test incrementally. This Skill generates phased upgrade plans with actionable steps, migration guidance, and risk assessment so you can execute upgrades methodically instead of all at once.

Yes. This Skill applies to both frontend and backend JavaScript and TypeScript projects using npm, Yarn, or PNPM. It parses package manifests from any project structure, analyzes version gaps, and produces upgrade plans regardless of whether you're upgrading React libraries, Node.js frameworks, or shared utilities.

The Skill outputs actionable upgrade reports containing an inventory of outdated packages, version gaps, identified breaking changes, step-by-step migration instructions, and risk assessments. You get both summary data and detailed guidance to execute upgrades confidently and track progress.

Not every package publishes detailed migration guides, but this Skill researches and compiles available guidance for packages with breaking changes. It surfaces what information exists, flags gaps where guides are unavailable, and provides enough context so you can locate official documentation or community resources independently.