Skip to main content
command

update-dependencies — Claude Code command for dependency updates

This command checks for outdated packages and security issues, then guides dependency updates by strategy. Use it for routine upgrades or a security-focused pass.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command setup/update-dependencies
Open on GitHub

What update-dependencies does

The command inspects project manifests and lock files, then checks package versions and security issues. It looks for package.json, requirements.txt, or Cargo.toml and their corresponding lock files. Choose an update strategy with --patch, --minor, --major, or --security-only.

It lays out staged upgrades, with tests and build checks between stages. The workflow also calls for reviewing breaking changes and preparing rollback steps and documentation updates. The checks vary by stack: Node.js uses npm audit, while Python uses pip check, so confirm that the suggested command fits the package manager in your project.

What it helps with

  • find outdated packages in a project
  • check dependencies for security issues
  • limit upgrades to security fixes
  • stage package updates with checks between them
  • prepare rollback and migration notes

Example prompts for the agent

  • Check the project and apply security-only dependency updates: /update-dependencies --security-only.
  • Review patch upgrades and test the project between stages: /update-dependencies --patch.
  • Assess major version upgrades, including breaking changes: /update-dependencies --major.

How to install update-dependencies

1claude-code-templates

npx claude-code-templates@latest --command setup/update-dependencies

2Manually: put the files in place

.claude/commands/update-dependencies.md

Call it with /update-dependencies. For all projects use ~/.claude/commands/

Questions about update-dependencies

How do I install update-dependencies in Claude Code?

Run npx claude-code-templates@latest --command setup/update-dependencies. The command file is at .claude/commands/update-dependencies.md.

What does update-dependencies do?

It checks package versions and security issues, then guides dependency upgrades with testing and compatibility checks. Pass a strategy such as --patch or --security-only.

Which update strategies can I use?

Choose --patch, --minor, --major, or --security-only. The workflow calls for checks between upgrade stages.

Source text

update-dependencies.md · MIT
---
allowed-tools: Read, Write, Edit, Bash
argument-hint: "[update-strategy] | --patch | --minor | --major | --security-only"
description: Update and modernize project dependencies with comprehensive testing and compatibility checks
---

# Update Dependencies

Update and modernize project dependencies with safety checks: **$ARGUMENTS**

## Current Dependencies State

- Package manager: @package.json or @requirements.txt or @Cargo.toml (detect package manager)
- Outdated packages: !`npm outdated 2>/dev/null || pip list --outdated 2>/dev/null || echo "Manual check needed"`
- Security issues: !`npm audit --audit-level=moderate 2>/dev/null || pip check 2>/dev/null || echo "Run security audit"`
- Lock files: @package-lock.json or @poetry.lock or @Cargo.lock

## Task

Systematically update project dependencies with comprehensive testing and compatibility validation:

**Update Strategy**: Use $ARGUMENTS to specify patch updates, minor updates, major updates, or security-only updates

**Update Process**:
1. **Dependency Analysis** - Audit current versions, identify outdated packages, assess security vulnerabilities
2. **Impact Assessment** - Check changelogs, breaking changes, deprecation warnings, compatibility matrix
3. **Staged Updates** - Apply patch updates first, then minor, finally major versions with testing between stages
4. **Testing & Validation** - Run full test suite, build verification, integration testing, performance checks
5. **Rollback Strategy** - Document changes, create restore points, maintain rollback procedures
6. **Documentation Updates** - Update README, dependencies list, migration guides, team notifications

**Safety Features**: Automated testing between updates, dependency conflict resolution, security vulnerability prioritization.

**Output**: Updated dependency manifest with comprehensive testing results, security audit report, and upgrade documentation.

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for DevOps and infrastructure →

From the same set495

The whole set →
vercel-edge-function Generate a TypeScript starter for a Vercel Edge Function, with request handlers and examples for geolocation or JWT checks. Use it when adding an edge API route to a Next.js project. 364installs vercel-environment-sync A hook that inspects environment variables after an .env edit and points you to the right Vercel sync commands. Useful when local and deployed values drift apart. 363installs prepare-release Automates software release preparation by validating git status, bumping semantic versions, running test suites, and generating changelogs. 363installs test-quality-analyzer Review test coverage, assertion quality, maintainability, and performance with one command. Use it to find gaps and decide what to improve in a test suite. 356installs developer-growth-analysis Reads your recent Claude chat history, spots skill gaps in your work, and sends a growth report to your Slack DMs. 355installs log Writes a finished task's report into your tracker or notes: time spent, status, commits. Useful when the coding happens in Claude but the record lives in Linear or Obsidian. 351installs create-worktrees Pulls every open pull request through GitHub CLI and sets up a separate git worktree for each branch under ./tree/. Useful when you want several PRs checked out at once without switching branches in the main checkout. 351installs setup-ci-cd-pipeline Configures CI/CD pipelines for GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins with automated testing, security gates, and deployment flows. 346installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor