Claude-code-templates dependency-updater

Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts for major versions, diagnoses and fixes dependency issues.

install
source · Clone the upstream repo
git clone https://github.com/davila7/claude-code-templates
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/davila7/claude-code-templates "$T" && mkdir -p ~/.claude/skills && cp -r "$T/cli-tool/components/skills/development/dependency-updater" ~/.claude/skills/davila7-claude-code-templates-dependency-updater && rm -rf "$T"
manifest: cli-tool/components/skills/development/dependency-updater/SKILL.md
source content

Dependency Updater

Smart dependency management for any language with automatic detection and safe updates.


Quick Start

update my dependencies

The skill auto-detects your project type and handles the rest.


Triggers

TriggerExample
Update dependencies"update dependencies", "update deps"
Check outdated"check for outdated packages"
Fix dependency issues"fix my dependency problems"
Security audit"audit dependencies for vulnerabilities"
Diagnose deps"diagnose dependency issues"

Supported Languages

LanguagePackage FileUpdate ToolAudit Tool
Node.jspackage.json
taze
npm audit
Pythonrequirements.txt, pyproject.toml
pip-review
safety
,
pip-audit
Gogo.mod
go get -u
govulncheck
RustCargo.toml
cargo update
cargo audit
RubyGemfile
bundle update
bundle audit
Javapom.xml, build.gradle
mvn versions:*
mvn dependency:*
.NET*.csproj
dotnet outdated
dotnet list package --vulnerable

Quick Reference

Update TypeVersion ChangeAction
FixedNo
^
or
~
Skip (intentionally pinned)
PATCH
x.y.z
x.y.Z
Auto-apply
MINOR
x.y.z
x.Y.0
Auto-apply
MAJOR
x.y.z
X.0.0
Prompt user individually

Workflow

User Request
    │
    ▼
┌─────────────────────────────────────────────────────┐
│ Step 1: DETECT PROJECT TYPE                         │
│ • Scan for package files (package.json, go.mod...) │
│ • Identify package manager                          │
├─────────────────────────────────────────────────────┤
│ Step 2: CHECK PREREQUISITES                         │
│ • Verify required tools are installed               │
│ • Suggest installation if missing                   │
├─────────────────────────────────────────────────────┤
│ Step 3: SCAN FOR UPDATES                            │
│ • Run language-specific outdated check              │
│ • Categorize: MAJOR / MINOR / PATCH / Fixed         │
├─────────────────────────────────────────────────────┤
│ Step 4: AUTO-APPLY SAFE UPDATES                     │
│ • Apply MINOR and PATCH automatically               │
│ • Report what was updated                           │
├─────────────────────────────────────────────────────┤
│ Step 5: PROMPT FOR MAJOR UPDATES                    │
│ • AskUserQuestion for each MAJOR update             │
│ • Show current → new version                        │
├─────────────────────────────────────────────────────┤
│ Step 6: APPLY APPROVED MAJORS                       │
│ • Update only approved packages                     │
├─────────────────────────────────────────────────────┤
│ Step 7: FINALIZE                                    │
│ • Run install command                               │
│ • Run security audit                                │
└─────────────────────────────────────────────────────┘

Commands by Language

Node.js (npm/yarn/pnpm)

# Check prerequisites
scripts/check-tool.sh taze "npm install -g taze"

# Scan for updates
taze

# Apply minor/patch
taze minor --write

# Apply specific majors
taze major --write --include pkg1,pkg2

# Monorepo support
taze -r  # recursive

# Security
npm audit
npm audit fix

Python

# Check outdated
pip list --outdated

# Update all (careful!)
pip-review --auto

# Update specific
pip install --upgrade package-name

# Security
pip-audit
safety check

Go

# Check outdated
go list -m -u all

# Update all
go get -u ./...

# Tidy up
go mod tidy

# Security
govulncheck ./...

Rust

# Check outdated
cargo outdated

# Update within semver
cargo update

# Security
cargo audit

Ruby

# Check outdated
bundle outdated

# Update all
bundle update

# Update specific
bundle update --conservative gem-name

# Security
bundle audit

Java (Maven)

# Check outdated
mvn versions:display-dependency-updates

# Update to latest
mvn versions:use-latest-releases

# Security
mvn dependency:tree
mvn dependency-check:check

.NET

# Check outdated
dotnet list package --outdated

# Update specific
dotnet add package PackageName

# Security
dotnet list package --vulnerable

Diagnosis Mode

When dependencies are broken, run diagnosis:

Common Issues & Fixes

IssueSymptomsFix
Version Conflict"Cannot resolve dependency tree"Clean install, use overrides/resolutions
Peer Dependency"Peer dependency not satisfied"Install required peer version
Security Vuln
npm audit
shows issues
npm audit fix
or manual update
Unused DepsBloated bundleRun
depcheck
(Node) or equivalent
Duplicate DepsMultiple versions installedRun
npm dedupe
or equivalent

Emergency Fixes

# Node.js - Nuclear reset
rm -rf node_modules package-lock.json
npm cache clean --force
npm install

# Python - Clean virtualenv
rm -rf venv
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt

# Go - Reset modules
rm go.sum
go mod tidy

Security Audit

Run security checks for any project:

# Node.js
npm audit
npm audit --json | jq '.metadata.vulnerabilities'

# Python
pip-audit
safety check

# Go
govulncheck ./...

# Rust
cargo audit

# Ruby
bundle audit

# .NET
dotnet list package --vulnerable

Severity Response

SeverityAction
CriticalFix immediately
HighFix within 24h
ModerateFix within 1 week
LowFix in next release

Anti-Patterns

AvoidWhyInstead
Update fixed versionsIntentionally pinnedSkip them
Auto-apply MAJORBreaking changesPrompt user
Batch MAJOR promptsLoses contextPrompt individually
Skip lock fileIrreproducible buildsAlways commit lock files
Ignore security alertsVulnerabilitiesAddress by severity

Verification Checklist

After updates:

  • Updates scanned without errors
  • MINOR/PATCH auto-applied
  • MAJOR updates prompted individually
  • Fixed versions untouched
  • Lock file updated
  • Install command ran
  • Security audit passed (or issues noted)

<details> <summary><strong>Deep Dive: Project Detection</strong></summary>

The skill auto-detects project type by scanning for package files:

File FoundLanguagePackage Manager
package.json
Node.jsnpm/yarn/pnpm
requirements.txt
Pythonpip
pyproject.toml
Pythonpip/poetry
Pipfile
Pythonpipenv
go.mod
Gogo modules
Cargo.toml
Rustcargo
Gemfile
Rubybundler
pom.xml
JavaMaven
build.gradle
Java/KotlinGradle
*.csproj
.NETdotnet

Detection order matters for monorepos:

  1. Check current directory first
  2. Then check for workspace/monorepo patterns
  3. Offer to run recursively if applicable
</details> <details> <summary><strong>Deep Dive: Node.js with taze</strong></summary>

Prerequisites

# Install taze globally (recommended)
npm install -g taze

# Or use npx
npx taze

Smart Update Flow

# 1. Scan all updates
taze

# 2. Apply safe updates (minor + patch)
taze minor --write

# 3. For each major, prompt user:
#    "Update @types/node from ^20.0.0 to ^22.0.0?"
#    If yes, add to approved list

# 4. Apply approved majors
taze major --write --include approved-pkg1,approved-pkg2

# 5. Install
npm install  # or pnpm install / yarn

Auto-Approve List

Some packages have frequent major bumps but are backward-compatible:

PackageReason
lucide-react
Icon library, majors are additive
@types/*
Type definitions, usually safe
</details> <details> <summary><strong>Deep Dive: Version Strategies</strong></summary>

Semantic Versioning

MAJOR.MINOR.PATCH (e.g., 2.3.1)

MAJOR: Breaking changes - requires code changes
MINOR: New features - backward compatible
PATCH: Bug fixes - backward compatible

Range Specifiers

SpecifierMeaningExample
^1.2.3
Minor + Patch OK
>=1.2.3 <2.0.0
~1.2.3
Patch only
>=1.2.3 <1.3.0
1.2.3
Exact (fixed)Only
1.2.3
>=1.2.3
At leastAny
>=1.2.3
*
AnyLatest (dangerous)

Recommended Strategy

{
  "dependencies": {
    "critical-lib": "1.2.3",      // Exact for critical
    "stable-lib": "~1.2.3",       // Patch only for stable
    "modern-lib": "^1.2.3"        // Minor OK for active
  }
}
</details> <details> <summary><strong>Deep Dive: Conflict Resolution</strong></summary>

Node.js Conflicts

Diagnosis:

npm ls package-name      # See dependency tree
npm explain package-name # Why installed
yarn why package-name    # Yarn equivalent

Resolution with overrides:

// package.json
{
  "overrides": {
    "lodash": "^4.18.0"
  }
}

Resolution with resolutions (Yarn):

{
  "resolutions": {
    "lodash": "^4.18.0"
  }
}

Python Conflicts

Diagnosis:

pip check
pipdeptree -p package-name

Resolution:

# Use virtual environment
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt

# Or use constraints
pip install -c constraints.txt -r requirements.txt
</details>

Script Reference

ScriptPurpose
scripts/check-tool.sh
Verify tool is installed
scripts/run-taze.sh
Run taze with proper flags

Related Tools

ToolLanguagePurpose
tazeNode.jsSmart dependency updates
npm-check-updatesNode.jsAlternative to taze
pip-reviewPythonInteractive pip updates
cargo-editRustCargo dependency management
bundler-auditRubySecurity auditing