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.
npx -y skills add decebals/claude-code-java --skill architecture-review --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
cursor/plugins
github/awesome-copilot
alirezarezvani/claude-skills
microsoft/win-dev-skills