architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
npx skills add majiayu000/claude-skill-registry --skill architecture-review-decebals-claude-code-java --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | --- ## Package Organization Strategies ### Package-by-Layer (Traditional) ``` com.example.app/ ├── controller/ │ ├── UserController.java │ ├── OrderController.java │ └── ProductController.java ├── service/ │ ├── UserService.java │ ├── OrderService.java │ └── ProductService.java ├── repository/ │ ├── UserRepository.java │ ├── OrderReposit
- When to Use
- Quick Reference: Architecture Smells
- Package Organization Strategies
- Package-by-Layer (Traditional)
- Package-by-Feature (Recommended)
- Hexagonal/Clean Architecture
- Dependency Direction Rules
- The Golden Rule
- Violations to Flag
- Architecture Review Checklist
- 1. Package Structure
- 2. Dependency Direction
- 3. Layer Boundaries
- 4. Module Boundaries
Package structure overview find src/main/java -type d | head -30 Largest packages (potential god packages) find src/main/java -name "*.java" | xargs dirname | sort | uniq -c | sort -rn | head -10 Check for framework imports in domain grep -r "import org.springframework" src/main/java/*/domain/ 2>/dev/null grep -r "import javax.persistence" src/main/java/*/domain/ 2>/dev/null Find circular dependencies (look for bidirectional imports) Check if package A imports from B and B imports from A
What does the architecture-review skill do?
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill architecture-review-decebals-claude-code-java --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.