dependency-analyzer

name	dependency-analyzer
description	Analyzes project dependencies, detects outdated packages, identifies breaking changes, and suggests safe update strategies. Helps maintain dependency health and security.
version	1.0.0
model	sonnet
invoked_by	both
user_invocable	true
tools	["Read","Write","Edit","Bash","Glob","Grep"]
best_practices	["Analyze package.json/requirements.txt/go.mod","Check for security vulnerabilities","Identify breaking changes","Suggest update strategies","Validate compatibility"]
error_handling	graceful
streaming	supported
templates	["dependency-report","update-plan","security-audit"]
verified	false
lastVerifiedAt	"2026-02-19T05:29:09.098Z"
source	builtin
trust_score	100
provenance_sha	30a049f886416e48

Dependency Analyzer Skill

Dependency Analyzer Skill - Analyzes project dependencies, detects outdated packages, identifies breaking changes, and suggests safe update strategies. - Analyzing dependency health - Planning dependency updates - Detecting security vulnerabilities - Identifying breaking changes - Validating compatibility

Step 1: Identify Dependency Files

Locate dependency files:

• package.json (Node.js)
• requirements.txt (Python)
• go.mod (Go)
• Cargo.toml (Rust)
• pom.xml (Java/Maven)

Step 2: Analyze Dependencies

Examine dependencies:

• Read dependency files
• Check versions
• Identify outdated packages
• Note version constraints

Step 3: Semantic Versioning Analysis

Analyze version numbers using semantic versioning (semver):

1. Parse version numbers:

   • Extract major.minor.patch from version strings
   • Handle version ranges (^, ~, >=, etc.)
   • Identify exact vs range versions

2. Detect major version bumps:

   • Compare current version with latest available
   • Identify major version changes (e.g., 1.x.x -> 2.x.x)
   • Flag major updates as potentially breaking

3. Check changelogs for breaking changes:

   • For major version updates: Trigger web search (Exa/WebFetch) to research breaking changes
   • Look for "BREAKING CHANGE" markers in changelogs
   • Check migration guides
   • Review release notes for breaking changes
   • Document specific breaking changes found

4. Semantic Versioning Rules:

   • Major version (X.0.0): Breaking changes likely, requires code changes
   • Minor version (0.X.0): New features, backward compatible
   • Patch version (0.0.X): Bug fixes, backward compatible

5. Breaking Change Detection:

   • Parse changelog entries for breaking change indicators
   • Identify deprecated APIs
   • Check for removed features
   • Document migration requirements

**Integration with DevOps Agent**: - Manages dependency updates - Implements update strategies - Validates compatibility **Dependency Health Report** **Example Commands**: