architecture-review

Analyze Java project architecture for package boundaries, dependency direction, and layering.

1|Updated May 30, 2025
One-click install
npx skills add https://github.com/mzffreyvazov/yt-to-spotify2 --skill architecture-review-mzffreyvazov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/mzffreyvazov/yt-to-spotify2/tree/main/.agents/skills/architecture-review
Command: npx skills add https://github.com/mzffreyvazov/yt-to-spotify2 --skill architecture-review-mzffreyvazov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes macro-level Java project architecture to surface structure, module boundaries, and dependency direction for healthier design.

Core Features & Use Cases

  • Package structure assessment: identifies organization, cohesion, and boundary clarity across modules.
  • Dependency direction checks: flags violations where outer layers leak into domain or application core.
  • Architecture-style evaluation: assesses alignment with common patterns like by-layer, by-feature, or hexagonal architectures.
  • Use Case: Before refactoring, quickly verify that boundaries are respected and architectural smells are surfaced.

Quick Start

Request an architectural review of a codebase to surface layering and dependency issues.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I identify architectural smells in a Java project?

Analyze the Java project's package boundaries, dependency direction, and layer organization to surface structural violations where outer layers leak into the domain core, providing a structured checklist for healthier design.

What is the best way to check for dependency direction violations in clean architecture?

Check for dependency direction violations by evaluating package structure and flagging instances where outer layers leak into the application core, ensuring adherence to clean or hexagonal architecture patterns.

How do I validate adherence to hexagonal architecture during a code review?

Validate hexagonal architecture adherence by evaluating package organization and module boundaries against architectural patterns, confirming that dependency directions respect the isolation of the domain core from external leaks.

Can I assess package structure and module boundaries before refactoring a codebase?

Yes, you can assess package structure and module boundaries before refactoring to quickly verify that architectural constraints are respected, identifying cohesion issues and boundary clarity across modules.

Does this architecture review work with by-feature and by-layer code organization?

Yes, the architecture review evaluates alignment with common architectural styles including by-feature and by-layer organization, assessing how well the package structure supports these macro-level patterns.