What problem does it solve? Upgrading npm packages often breaks builds silently: peer dependency conflicts slip through installs, formatter updates reformat hundreds of files, and new linter rules flood the tree with findings. This Skill provides a disciplined procedure for raising dependency versions without losing the real cause of failures. ## Core Features & Use Cases - Peer-range upper bound selection: Raise a package to the last version within every dependent's peer range, verified with npm view commands rather than guessing from the registry. - Ordered verification pipeline: Exact versions in package.json, install with lockfile in the same commit, CSS custom property checks against installed package sources, build before linters, then tests and browser verification. - Reformatting and linter rule policy: Decide which reformatted files to keep based on linter coverage, and handle new linter rules via documented config switches or targeted eslint-disable-next-line comments. - Use Case: After a Dependabot alert on a transitive dependency, follow the pattern to pick the correct upper bound, verify removed styling properties with grep, and land the update in its own branch and commit. ## Quick Start Ask the assistant to apply the dependencies-upgrade pattern to raise a specific package version and verify the build, linters, and tests in the correct order.
