smart-dependency-updaterlisted

# Smart Dependency Updater Use this skill to perform dependency updates as engineering work, not as mechanical version bumps. The default outcome is a portfolio of focused, review-ready dependency groups. Each group bundles related packages, explains what changed upstream, assesses local impact, runs the repository's validation suite, and adopts newly useful dependency capabilities when they improve the local code. Treat every update as a small migration and delivery unit. Do not stop after updating one easy package or writing a chat summary unless the user explicitly asked for that narrower outcome. A good outcome is a set of review-ready groups where reviewers and automation can see why the versions belong together, what changed in those dependencies, what local risk was checked, which tests were run, and whether the project now benefits from new APIs, fixed limitations, or changed defaults. ## New Dependency Introduction Treat a new external dependency as a focused compatibility decision, not as a repository-wide update portfolio: 1. Establish the missing capability and check whether the repository, platform, or an existing direct dependency already provides it adequately. 2. Identify the owning ecosystem, package manager, runtime and framework constraints, peer requirements, supported toolchain, and lockfile boundary. 3. Verify the current stable release through registry metadata or an official upstream source. Avoid prereleases, release candidates, canaries