skills.rest
decebals
decebalsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-review

Analyze Java project architecture by summarizing package structure, layering, and dependency flow.

700|137|Updated Jan 30, 2026
Search Tags:#architecture#java#code-review#clean-architecture#package-structure#dependency-direction
One-click install
npx skills add https://github.com/decebals/claude-code-java --skill architecture-review-decebals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/decebals/claude-code-java/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/decebals/claude-code-java --skill architecture-review-decebals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Macro-level Java architecture analysis to reveal package structure, layering, module boundaries, and dependency direction, enabling teams to improve maintainability and alignment with architectural styles.

Core Features & Use Cases

  • Analyze package organization (by-layer, by-feature, or hexagonal) and identify cohesion and boundaries.
  • Evaluate dependency direction to ensure inner-domain independence and leakage prevention.
  • Detect architectural smells like god packages, circular dependencies, and leaky abstractions.
  • Produce high-level architectural risk reports and prioritized recommendations for refactors.
  • Use cases include initial architecture review, pre-refactor assessments, and architecture-state evaluations.

Quick Start

Run an architecture review on the current project to generate a structured report.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I analyze Java project architecture for package structure and dependency flow?▼

Perform a macro-level architecture review to summarize package structure, layering, and dependency direction. It assesses module boundaries and coupling to reveal how well your project aligns with clean or hexagonal architecture patterns.

What are common architectural smells in Java package structure?▼

Common architectural smells include god packages, circular dependencies, and leaky abstractions. Detecting these issues during a macro-level review helps prevent inner-domain leakage and highlights architectural risks before refactoring.

Can I use this architecture review for pre-refactor assessments on codebases of different sizes?▼

Yes, this architecture review applies to real-world codebases of different sizes for pre-refactor assessments. It evaluates module boundaries and produces high-level architectural risk reports with prioritized improvement steps.

How does a macro-level code review detect clean architecture pattern violations?▼

A macro-level architecture review detects clean architecture violations by evaluating dependency direction and boundary cohesion. It identifies leaky abstractions and checks alignment with by-layer, by-feature, or hexagonal package organization patterns.

What is the best way to generate an architectural risk report for a Java project?▼

Run a macro-level architecture review on your Java project to generate a structured risk report. It identifies structural smells like circular dependencies and produces actionable recommendations with prioritized refactoring steps.

Related Skills

Explore More Software Engineering Skills→
mzffreyvazovmzffreyvazov

architecture-review

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

Community
Advanced
vitorsilvavitorsilva
1

architecture-compliance

Enforce architectural layer boundaries and dependency rules across the codebase.

Community
Advanced
mcj-codermcj-coder
1

component-boundary-ownership

Analyze deployment independence, team ownership, and coupling to define component boundaries.

Community
Advanced
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced