Dependency upgrade
Small, harness-neutral engineering skills for coding agents
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.
3 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.3 KB, 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.