arch-review

Analyze codebase architecture for layer violations and circular dependencies.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill arch-review-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/arch-review
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill arch-review-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to assess a codebase's architecture, detecting layer violations, circular dependencies, missing public APIs, and weak abstraction boundaries to improve maintainability and scalability.

Core Features & Use Cases

  • Performs ARCH-1 through ARCH-6 evaluations to identify architectural health issues.
  • Integrates with map-codebase outputs and optional arch-check results to produce a comprehensive architecture report.
  • Ideal for planning major refactors, onboarding new team members, or validating architectural health after large changes.

Quick Start

Run this skill after map-codebase to generate the durable architecture report.

Frequently Asked Questions about arch-review

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

FAQPage Schema
How do I audit code architecture for circular dependencies and layer violations?

You can audit code architecture by analyzing the repository structure and module graph to identify layer violations, circular dependencies, missing public APIs, and incomplete abstraction boundaries.

What is a code architecture audit and when do I need one?

A code architecture audit systematically assesses architectural health to improve maintainability and scalability. You need one during major refactors, when onboarding new team members, or after large codebase changes.

How do I check for missing public APIs and weak abstraction boundaries in my repository?

Checking for missing public APIs and weak abstraction boundaries requires analyzing the codebase architecture to evaluate structural health issues across ARCH-1 through ARCH-6 architectural evaluations.

Can I run an architecture audit on a codebase of any size?

Yes, architecture audits apply to projects of all sizes. You need access to the repository structure and module graph to produce a comprehensive architecture report.

What's the best way to validate architectural health after a major refactor?

The best way to validate architectural health after a refactor is to systematically audit the codebase for layer violations and circular dependencies, producing a durable architecture report and concise context brief.

Do I need to map my codebase before running an architecture analysis?

You should run map-codebase before this skill to generate the durable architecture report. The analysis integrates map-codebase outputs and optional arch-check results for comprehensive architectural evaluation.