architecture-review

Analyze Java project package layout, module boundaries, and dependency direction for architectural violations.

1|1|Updated Apr 16, 2026

Search Tags:#architecture #review #hexagonal #clean-architecture #module-boundaries #package-structure #dependency-direction

Ready to run

npx skills add https://github.com/iCesofT/awesome-ai --skill architecture-review-icesoft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/iCesofT/awesome-ai/tree/main/skills/01-planning-architecture-review
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill architecture-review-icesoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering to identify structural issues and opportunities for improvement.

Core Features & Use Cases

Assess package and module organization to highlight cohesion and coupling.
Detect dependency-direction violations and layering breaches to enforce clean architecture.
Produce actionable recommendations and a prioritized improvement plan for stakeholders.

Quick Start

Analyze a Java codebase to surface architectural smells and present remediation steps.

Frequently Asked Questions about architecture-review

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

FAQPage Schema

How do I check for architecture violations in a Java project?▼

Detecting Java architecture violations involves analyzing package structure, module boundaries, and dependency direction to identify layering breaches and produce a prioritized improvement plan for stakeholders.

What are common clean architecture smells in Java module boundaries?▼

Common clean architecture smells in Java module boundaries include improper dependency direction, high coupling between modules, and layering breaches where inner layers depend on outer layers instead of isolating domain logic.

How do I audit package structure for hexagonal architecture compliance?▼

Auditing package structure for hexagonal architecture compliance requires evaluating dependency directions to ensure core domain logic remains isolated, identifying structural issues where modules bypass defined ports and adapters boundaries.

Can I review a large Java codebase for dependency direction issues?▼

Yes, you can review a large Java codebase for dependency direction issues by analyzing the macro-level package layout and module boundaries to enforce clean architecture rules across all modules.

What is the best way to assess module coupling and cohesion in Java?▼

The best way to assess module coupling and cohesion in Java is to analyze the project's package organization and dependency direction, highlighting structural issues and actionable recommendations for improvement.