Skill: Review Architecture

Purpose

Review code for architecture concerns only. Do not define scope (diff vs codebase) or perform language/framework/security analysis; those are separate atomic skills. Emit a findings list in the standard format for aggregation. Focus on module and layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling and extension points.

Core Objective

Primary goal: Produce an architecture-focused findings list covering module/layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling for the given code scope.

Success Criteria (ALL must be met):

1. ✅ Architecture-only scope: Only architecture dimensions are reviewed; no scope selection, language/framework conventions, security, or performance analysis performed
2. ✅ All six architecture dimensions covered: Module/layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling are assessed where relevant
3. ✅ Findings format compliant: Each finding includes Location, Category (cognitive-architecture), Severity, Title, Description, and optional Suggestion
4. ✅ Location-precise references: All findings reference specific modules, packages, or files (not vague descriptions)
5. ✅ Actionable output: Each finding provides a concrete refactoring suggestion or improvement direction