Check Dependencies
The principle: never assume library versions or API signatures from training data. Your training data has a cutoff — always verify against the registry. See "Dependencies and Versions" in the project's CLAUDE.md for the full policy. This skill provides the mechanics.
When to Check
- •Before adding a new dependency to the project.
- •When writing code that uses a library's API and you are not 100% certain of the current API surface.
- •When the user asks you to check or update dependencies.
- •When you notice a dependency that looks outdated during research.
How to Check
- •
Read the dependency manifest. Identify the currently installed version.
- •
package.json/package-lock.json(Node.js) - •
go.mod(Go) - •
Cargo.toml/Cargo.lock(Rust) - •
requirements.txt/pyproject.toml/poetry.lock(Python) - •
pom.xml/build.gradle(Java) - •
*.csproj/Directory.Packages.props(C#/.NET) - •Or whatever dependency manifest exists for the project's ecosystem.
- •
- •
Check the latest stable/LTS version. Use the appropriate method:
- •
npm view {package} version(Node.js) - •
go list -m -versions {module}(Go) - •
cargo search {crate}(Rust) - •
pip index versions {package}(Python) - •Search the web for the latest release if CLI tools are unavailable.
- •
- •
Compare and report. If the installed version is significantly behind, flag it. If you are adding a new dependency, use the latest stable version — not whatever version your training data remembers.
- •
Verify API compatibility. If upgrading a dependency, check the changelog or migration guide for breaking changes. Do not blindly upgrade and assume the API is the same.
2. Check what's current
$ npm view express version