Architecture Reviewer

Reviews code changes for architectural compliance, module boundaries, and design integrity.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill architecture-reviewer-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Architecture Reviewer
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/agents/architecture-reviewer
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill architecture-reviewer-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases drift from their intended architecture over time, introducing circular dependencies, bloated public APIs, and inconsistent patterns that erode maintainability. This Skill systematically reviews code changes against established project conventions to catch architectural violations before they merge. ## Core Features & Use Cases - Pattern Compliance Review: Reads AGENTS.md and project documentation to verify changed code follows established conventions and dependency flow rules. - Module Boundary Enforcement: Detects circular dependencies, checks that public API surfaces stay minimal, and validates layer isolation using frameworks like ArchUnit, import-linter, dependency-cruiser, and arch-go. - Parallel Multi-Module Review: Spawns subagents to review each module boundary in parallel for changes spanning multiple modules, and coordinates findings with performance and security reviewers. - Use Case: During a pull request touching several packages, the reviewer flags a new import that creates a circular dependency between the domain and infrastructure layers, classifying it as a VIOLATION with a suggested fix. ## Quick Start Ask the agent to review the current code changes for architectural compliance and report any violations, drift, or suggestions.

Frequently Asked Questions about Architecture Reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code for architectural compliance automatically?▼

The reviewer reads AGENTS.md and project docs to learn established patterns, then checks changed code against them for module boundary violations, circular dependencies, and API surface bloat. Findings are reported as VIOLATION, DRIFT, or SUGGESTION.

How to detect circular dependencies in a multi-module project?▼

The reviewer verifies that dependencies flow in the correct direction and that module boundaries are respected. It also consults executable layer isolation rules using tools like ArchUnit, import-linter, dependency-cruiser, and arch-go per language.

What tools enforce architecture rules in different languages?▼

The skill references architecture test frameworks per language: ArchUnit for JVM projects, import-linter for Python, dependency-cruiser for JavaScript, and arch-go for Go. These encode layer isolation rules as executable tests.

Can architecture review handle changes spanning multiple modules?▼

Yes. For cross-module changes, the reviewer spawns parallel subagents to review each module boundary independently. Cross-cutting findings are shared with performance-reviewer and security-reviewer teammates via SendMessage.

What is the difference between a VIOLATION and DRIFT finding?▼

A VIOLATION breaks established architecture, such as a circular dependency or wrong dependency direction. DRIFT means the code is functional but inconsistent with project conventions, while SUGGESTION marks an improvement opportunity.