Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when raising the version of an INCOMING dependency. Fires on: "bump the dependency", "update the library", "upgrade <lib>", "refresh the lockfile", "dependencies are outdated". Bumps the version in the single source of truth, syncs the lockfile, rebuilds, revalidates, and fixes any pinned references.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -29% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -26% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -28% | 0% |
| case-17 | ✗→✓ | ▲ Improved | -23% | 0% |
| case-04 | ✓→✓ | ＝ Same ✓ | -2% | 0% |
A dependency version usually lives in more than one place. Bump the source of truth, then chase every pin — a half-bumped dependency is drift that compiles.
pom.xml dependency management, pyproject.toml, package.json. Bump there.
uv lock,npm install, etc.). Lockfile and manifest must move together — CI likely runs --locked / --frozen and will fail otherwise.
Dockerfiles, docs, .env examples, README badges — bump each. Consult .skills/change-map.yaml if a "new dependency" coupling is listed.
Testcontainers version). Do not "upgrade" those blindly — confirm before touching a pin the project marks as deliberate.
A dependency bump is not done until the suite is green.
surface it — do not silently paper over it.
Old → new version, every file touched, build/test result. If the build breaks, report the failing assertion — do not leave a half-applied bump.
Other measured skills in the registry, with their headline benchmark lift.