Dependency upgrade
Plan and execute dependency upgrades in small risk-ordered batches with changelog review, lockfile control, and verification after each batch. Use for outdated packages, security updates, or runtime/toolchain upgrades.From its SKILL.md
npx -y skills add kevinb361/agent-skills --skill dependency-upgradeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 189 tokens by cl100k_base, as published. Nobody here has run it
Dependency upgrades
Inventory
Detect the package manager, lockfiles, runtime constraints, and canonical test gate. Record current versions and identify direct versus transitive dependencies.
Classify upgrades:
- security-critical
- low-risk tooling or patch/minor
- runtime minor
- runtime major or toolchain migration
Read authoritative release notes for security updates, majors, and packages with known compatibility coupling.
Execution
Upgrade one coherent risk tier or coupled package family at a time. Preserve the existing package manager and lockfile. Do not mix unrelated code cleanup into upgrade changes.
After each batch:
- inspect manifest and lockfile changes
- run focused compatibility checks
- run the project's canonical gate
- investigate failures before proceeding
Keep runtime majors separate unless they must move together. Document required migrations, deprecations, and rollback points. Never claim a vulnerability is fixed without verifying the resolved dependency graph.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.