What problem does it solve? Java codebases in Spring Boot projects often drift into inconsistent naming, mutable state, poor Optional usage, and unclear exception handling, making reviews slow and maintenance costly. This Skill provides a concrete, example-driven standards reference so code is written and reviewed against one consistent set of rules. ## Core Features & Use Cases - Naming and Structure Conventions: Enforces PascalCase classes, camelCase methods, UPPER_SNAKE_CASE constants, and a standard Maven/Gradle package layout (config, controller, service, repository, domain, dto, util). - Immutability and Modern Java: Promotes records, final fields, sealed classes, and pattern matching for Java 17+, plus correct Optional and stream usage. - Exceptions, Logging, and Testing: Guides domain-specific exceptions, SLF4J logging patterns, null handling with Bean Validation, and JUnit 5 + AssertJ + Mockito testing expectations. - Use Case: When reviewing a pull request that returns null from a repository method and catches generic Exception, apply these standards to refactor it into an Optional-returning method that throws a domain-specific MarketNotFoundException. ## Quick Start Review this Spring Boot service class against the Java coding standards and list every violation with a corrected version.
