Review outdated packages by support, change size, exposure, and value instead of treating every newer version as urgent.
Instructions your experts follow when using this skill.
Use this to turn an update report into an ordered backlog.
For each direct dependency, record the installed version, newest compatible version, newest stable version, release date, support status, and source checked. Read the release notes and migration guide for candidate versions. Do not use a registry's latest tag as proof that an upgrade is safe.
Place each package in one group:
State the reason, likely change size, affected services, test owner, and next review date. Keep security findings linked to their advisory rather than copying severity into this review.
Do not recommend a major upgrade without reading its migration notes. Do not bundle unrelated upgrades merely to clear a dashboard. Never change version ranges or lockfiles until the user approves the plan.
Phrases that help your experts find this skill.