rescue-depslisted
Install: claude install-skill vivekbhange-hub/legacy-rescue-skill
# rescue-deps
An old dependency tree is a slow-moving incident: security fixes you cannot take, a runtime
the host will drop, a framework nobody can hire for. Upgrading everything at once is how
rescues fail. This skill takes stock of what the project runs on, rates each gap, and lays out
an upgrade path where every step is small, tested by the characterization suite and revertible
on its own. It reads and plans; it changes nothing until the user approves a step.
## Inputs
- `$ARGUMENTS`: project path, default `.`.
- `rescue/map.md` for the list of deployables and manifests, if present.
- The production runtime version if the user knows it (Dockerfile base image, buildpack,
`.nvmrc`, `.python-version`, `runtime.txt`, `global.json`, CI matrix).
## Output
- `rescue/deps.md`: runtime table, upgrade path with risk per step, breaking-change checklist.
- `rescue/deps-*.json`: raw tool output kept as evidence.
## Steps
1. **Find every manifest and lockfile.** Glob for package.json, requirements*.txt,
pyproject.toml, Pipfile, go.mod, pom.xml, build.gradle*, Gemfile, composer.json, *.csproj,
Cargo.toml, mix.exs. Note which have lockfiles. A manifest without a lockfile means
builds are not reproducible: that is risk number one.
2. **Pin the runtimes.** Record the declared runtime for each deployable and where it is
declared (Dockerfile `FROM`, engines field, `.nvmrc`, `python_requires`, `<java.version>`,
`go` directive, `TargetFramework`, CI matrix). Mismatches