Architecture Review

This gives Claude a structured way to analyze Java projects from 30,000 feet instead of getting lost in method-level details. When someone asks "is this clean architecture?" or "review our package structure," it checks dependency direction, spots leaky abstractions, and flags anti-patterns like domain entities littered with JPA annotations or a util package that's become a junk drawer. The skill includes quick reference tables for architecture smells, concrete examples of package-by-feature versus hexagonal organization, and a checklist covering everything from circular dependencies to whether you could actually extract a module without surgery. It knows the difference between reviewing structure and reviewing code quality, which is harder to teach an LLM than you'd think.

skills.sh installs: 374
GitHub stars: 771
last updated: Feb 8, 2026

View on GitHub

Install

$ npx -y skills add decebals/claude-code-java --skill architecture-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Architecture Review Skill

Analyze project structure at the macro level - packages, modules, layers, and boundaries.

When to Use

User asks "review the architecture" / "check project structure"
Evaluating package organization
Checking dependency direction between layers
Identifying architectural violations
Assessing clean/hexagonal architecture compliance

Quick Reference: Architecture Smells

Smell	Symptom	Impact
Package-by-layer bloat	`service/` with 50+ classes	Hard to find related code
Domain → Infra dependency	Entity imports `@Repository`	Core logic tied to framework
Circular dependencies	A → B → C → A	Untestable, fragile
God package	`util/` or `common/` growing	Dump for misplaced code
Leaky abstractions	Controller knows SQL	Layer boundaries violated