java-code-review

# Java Code Review Perform a focused, evidence-based review of Java code and write the findings to `review.md` in the repository root unless the user specifies another location. This skill reviews code; do not modify production code unless the user explicitly asks for fixes. ## Establish the review scope 1. If the user explicitly specifies files, classes, packages, commits, or a diff, use that scope and do not silently broaden it. 2. Otherwise inspect the git worktree and review modified, added, or renamed files. Use `git status --short` and the relevant `git diff` (including staged changes when present). For renamed files, review the resulting file and the meaningful diff. 3. Include only Java and Java-adjacent files relevant to behavior (for example, tests, SQL migrations, configuration, or API schemas) when they affect the reviewed Java code. State the selected scope in the report. 4. Read enough surrounding code, callers, tests, configuration, and interfaces to validate each finding. Do not report a concern based only on a name or a generic best practice. ## Review for - **Potential bugs:** incorrect conditions, null/empty handling, state or transaction errors, exception handling, resource leaks, concurrency issues, security or authorization gaps, API/serialization mismatches, persistence mistakes, and boundary cases. - **Duplicate code:** repeated logic, copy-pasted branches, duplicated mappings/validation, and abstractions that would...