Dependency upgrade
Reusable agent skills for real repository work: review, implementation, release, documentation, and project hygiene.
npx -y skills add bakerstreetco/skills --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
- 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
Upgrade project dependencies safely by inspecting manifests, lockfiles, changelogs, breaking changes, tests, and generated artifacts. Use when asked to update packages, bump frameworks, address dependency vulnerabilities, refresh lockfiles, or modernize SDK versions.
SKILL.md
1.5 KB, as published. Nobody here has run it
Dependency Upgrade
Use this skill to upgrade dependencies without turning the repo into an uncontrolled migration.
Workflow
- Identify package managers, manifests, lockfiles, runtime versions, and workspace structure.
- Inspect current dependency versions, direct versus transitive dependencies, and existing update conventions.
- Choose the smallest useful update set: one dependency, one ecosystem group, security patch group, or framework upgrade.
- Check release notes, changelogs, migration guides, and deprecations for breaking changes.
- Update manifests and lockfiles with the repo's package manager.
- Fix compile, lint, type, or test failures caused by the upgrade.
- Run focused tests plus the package manager's integrity checks.
- Document behavior changes, migration notes, and follow-up work when relevant.
Checks
- Lockfiles match manifests.
- Generated files are included only when the repo tracks them.
- Runtime and engine constraints still match CI and docs.
- Security fixes do not silently introduce major version changes unless requested.
- Deprecation warnings are handled or recorded.
Output
Summarize upgraded packages, version changes, breaking-change review, files changed, verification commands, and remaining risk.