| name | forge-dependency-review |
| description | Review project dependencies - outdated, unused, licenses, supply chain risks. Trigger when user types /forge-dependency-review or requests a dependency review.
|
/forge-dependency-review
Review project dependencies using AI reasoning.
Command
/forge-dependency-review [path] [--quick|--deep] [--markdown|--json] [--verbose]
Options
[path] — Target directory (default: current directory)--quick — Fast scan, focus on critical issues only--deep — Thorough scan, check all patterns--markdown — Output as markdown (default)--json — Output as JSON--verbose — Include detailed evidence
Purpose
Analyze project dependencies for:
- Outdated packages
- Unused dependencies
- Dependency tree issues
- License compatibility
- Supply chain risks
Workflow
Step 1: Understand Project
Use shared/analyzer/ to detect:
- Package manager
- Dependency files (package.json, go.mod, requirements.txt)
Step 2: Run Dependency Analysis
Execute analysis prompts:
- Outdated Detection (
prompts/outdated-detection.md)
- Unused Detection (
prompts/unused-detection.md)
- Dependency Tree (
prompts/dependency-tree.md)
- License Compatibility (
prompts/license-compatibility.md)
- Supply Chain Risk (
prompts/supply-chain-risk.md)
Step 3: Generate Report
Use shared/report/ to generate:
- Dependency Health Score (0-100)
- Risk analysis
- Update recommendations
Output Format
Follow the markdown report format generated by shared/report/markdown.ts. It MUST use the following layout:
Dependency Review Report
Project: [Project Name]
Path: [Project Path]
Language: [Primary Language]
Framework: [Detected Framework (optional)]
Date: [Timestamp]
Score
[Score]/100 (Grade: [Grade])
| Severity | Count |
|---|
| 🔴 Critical | [count] |
| 🟠 High | [count] |
| 🟡 Medium | [count] |
| 🔵 Low | [count] |
| ⚪ Info | [count] |
Executive Summary
Found [total] issues: [count] critical, [count] high, [count] medium, [count] low, [count] info.
🔍 Detailed Findings
[Severity Group (e.g. 🔴 Critical)]
| Title | Location | Description | Impact |
|---|
| [Finding Title] | [file-name]:[line] | [Description] | [Impact] |
📂 Code Evidence
Finding #[number]: [Finding Title]
[code snippet]
