| name | forge-architecture-review |
| description | Review project architecture - patterns, separation, modularity, SOLID. Trigger when user types /forge-architecture-review or requests an architecture review.
|
/forge-architecture-review
Review project architecture using AI reasoning.
Command
/forge-architecture-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 source code for:
- Design pattern usage
- Separation of concerns
- Module boundaries
- Technical debt
- SOLID principles compliance
Workflow
Step 1: Understand Project
Use shared/analyzer/ to detect:
- Repository type
- Primary language
- Framework
- Project structure
Step 2: Run Architecture Analysis
Execute analysis prompts:
- Design Patterns (
prompts/design-patterns.md)
- Separation of Concerns (
prompts/separation-of-concerns.md)
- Modularity (
prompts/modularity.md)
- Technical Debt (
prompts/technical-debt.md)
- SOLID Compliance (
prompts/solid-compliance.md)
Step 3: Generate Report
Use shared/report/ to generate:
- Architecture Score (0-100)
- Pattern analysis
- Refactoring recommendations
Output Format
Follow the markdown report format generated by shared/report/markdown.ts. It MUST use the following layout:
Architecture 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]
