Code Quality Review Skill

Knowledge for reviewing Java / Spring Boot changes: what to flag and how to recognize it. The review process, scope, and report format belong to the code-reviewer agent; project rules belong to the conventions skill.

No duplication: this skill holds only what no other skill states (generic Java quality, smells, REST semantics, detection signals). Project rules live in conventions, spring-boot, and jpa-patterns; the references here point to them and never restate them, so a rule change is made in one place.

When to Use

• "review this code" / "code review" / "check this PR"
• "refactor" / "clean this code" / "improve readability"
• "review API" / "check endpoints" / "REST review"
• Before merging a PR or releasing API changes

What to Load

Read only the references that match the changed files.