/arch-review - Architecture Review

Analyze code or system architecture and provide recommendations.

Usage

/arch-review [target] [scope]

Arguments:

• target - Directory, module, or "system" for full review
• scope - (optional) Focus: structure, patterns, dependencies, scalability

Examples

/arch-review src/
/arch-review src/services/ patterns
/arch-review system dependencies
/arch-review src/api/ scalability

What It Does

1. Analyzes architecture for:

   • Code organization and structure
   • Design pattern usage
   • Dependency management
   • Separation of concerns
   • SOLID principles adherence
   • Scalability considerations

2. Identifies:

   • Architectural anti-patterns
   • Coupling and cohesion issues
   • Missing abstractions
   • Technical debt areas
   • Improvement opportunities

Output Format

## Architecture Review: {target}

### Overview
{High-level assessment}

### Strengths
- {What's working well}

### Concerns

#### 1. {Issue Title}
- **Severity:** High/Medium/Low
- **Location:** {affected areas}
- **Issue:** {description}
- **Impact:** {consequences if not addressed}
- **Recommendation:** {suggested fix}

### Design Patterns
- **Used:** {patterns found}
- **Recommended:** {patterns that could help}

### Dependency Analysis
- **External deps:** X
- **Circular deps:** {any found}
- **Coupling score:** {assessment}

### Recommendations
1. {Priority recommendation}
2. {Secondary recommendation}

### Technical Debt Score
{Overall assessment}: X/10

Skill Used

skills/analysis/architecture/

When to Use Agent Instead

Use the Software Architect agent when:

• Major architectural decisions needed
• ADR documentation required
• System redesign being considered
• Cross-team architectural alignment needed