Dependency upgrade
Skill NSBen/skillfoundry/src/skillfoundry/data/starter_skills/dependency-upgrade
Use when a dependency is outdated or has a known vulnerability and you need to upgrade it safely with the right changelog and migration notes.From its SKILL.md
npx -y skills add NSBen/skillfoundry --skill dependency-upgradeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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 file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.2 KB, 166 tokens by cl100k_base, as published. Nobody here has run it
Dependency Upgrade
When to use
Use this skill when npm audit, pip-audit, or a version check flags an outdated or vulnerable dependency.
Steps
- Identify the current and latest versions and whether the bump is major.
- Read the release notes / changelog for breaking changes between the two.
- Check the project's lockfile and peer/version constraints.
- Apply the upgrade, then run the test suite and the build.
- Summarize the changes, risks, and any code edits the migration requires.
Examples
- "Upgrade requests to the latest secure version"
- "Is this major bump of react safe?"
References
Prefer minimal, reviewed bumps; for majors, isolate the upgrade in its own PR so regressions are easy to bisect.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.