dependency-analyzer
Analyzes project dependencies, detects outdated packages, identifies breaking changes, and suggests safe update strategies. Helps maintain dependency health and security.
How do I install this agent skill?
npx skills add https://github.com/oimiragieo/agent-studio --skill dependency-analyzerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The dependency-analyzer skill is a utility for managing project dependencies. It performs standard operations like reading configuration files, querying registries for updates, and conducting security audits. No malicious behavior or suspicious obfuscation was detected.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
2/10 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Dependency Analyzer Skill
<identity> Dependency Analyzer Skill - Analyzes project dependencies, detects outdated packages, identifies breaking changes, and suggests safe update strategies. </identity> <capabilities> - Analyzing dependency health - Planning dependency updates - Detecting security vulnerabilities - Identifying breaking changes - Validating compatibility </capabilities> <instructions> <execution_process>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):
-
Parse version numbers:
- Extract major.minor.patch from version strings
- Handle version ranges (^, ~, >=, etc.)
- Identify exact vs range versions
-
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
-
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
-
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
-
Breaking Change Detection:
- Parse changelog entries for breaking change indicators
- Identify deprecated APIs
- Check for removed features
- Document migration requirements
- Generate breaking change report
Step 4: Check for Updates
Check available updates:
- Query package registries
- Compare current vs latest versions
- Identify major/minor/patch updates
- Apply semantic versioning analysis
- Warn about breaking changes
Step 5: Security Audit
Check for vulnerabilities:
- Scan for known vulnerabilities
- Check security advisories
- Identify high-risk packages
- Suggest security updates
Step 6: Generate Report
Create dependency report:
- List outdated packages
- Identify breaking changes
- Suggest update strategy
- Provide migration guidance </execution_process>
Integration with Security Architect Agent:
- Reviews security vulnerabilities
- Validates security updates
- Ensures compliance </integration>
<best_practices>
- Regular Analysis: Analyze dependencies regularly
- Security First: Prioritize security updates
- Test Updates: Always test after updates
- Gradual Updates: Update incrementally
- Document Changes: Track update decisions </best_practices> </instructions>
# Dependency Health Report
## Summary
- Total Dependencies: 45
- Outdated: 12
- Vulnerable: 3
- Up to Date: 30
## Outdated Packages
- react: 18.0.0 -> 18.2.0 (minor update)
- next: 13.4.0 -> 14.0.0 (major update - breaking changes)
- typescript: 5.0.0 -> 5.3.0 (patch update)
## Security Vulnerabilities
- lodash: 4.17.20 (CVE-2021-23337) - Update to 4.17.21
- axios: 0.21.1 (CVE-2021-3749) - Update to 1.6.0
## Update Recommendations
1. Update patch versions (safe)
2. Review minor updates (low risk)
3. Plan major updates (breaking changes)
</formatting_example>
<formatting_example> Update Plan
# Dependency Update Plan
## Phase 1: Patch Updates (Safe)
- Update lodash: 4.17.20 -> 4.17.21
- Update typescript: 5.0.0 -> 5.3.0
## Phase 2: Minor Updates (Low Risk)
- Update react: 18.0.0 -> 18.2.0
- Update @types/node: 20.0.0 -> 20.10.0
## Phase 3: Major Updates (Breaking Changes)
- Update next: 13.4.0 -> 14.0.0
- Breaking changes: [List]
- Migration steps: [Steps]
- Testing required: [Tests]
</formatting_example> </examples>
<examples> <usage_example> **Example Commands**:# Analyze dependencies
Analyze dependencies for this project
# Check for updates
Check for dependency updates
# Security audit
Perform security audit of dependencies
# Generate update plan
Generate update plan for major version updates
</usage_example> </examples>
Rules
- Always check for security vulnerabilities first
- Research breaking changes before major updates
- Test thoroughly after any dependency update
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.md
After completing:
- New pattern ->
.claude/context/memory/learnings.md - Issue found ->
.claude/context/memory/issues.md - Decision made ->
.claude/context/memory/decisions.md
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/oimiragieo/agent-studio/dependency-analyzer">View dependency-analyzer on skillZs</a>