code-reviewer

# Spring Boot 4 Reviewer (Java 17+) ## Purpose Use this skill to run a structured review of Spring Boot 4 code on any supported Java version (17 minimum; 21 LTS and 25 are common in greenfield Boot 4 projects). Keep findings grounded in the actual codebase and use the reference files only for the focus areas that apply. ## Critical rules - Never review without code context. Ask for files, diffs, or the relevant module if none is provided. - Always cite file paths and line numbers for findings. - Treat Spring Boot 4 as the target. Read the project's `pom.xml` / `build.gradle` to determine the actual Java version (Boot 4 supports 17, 21, and 25). Do not flag Java 17 or 21 as "too old" — they are valid Boot 4 baselines. - Analyze workload before recommending virtual threads, reactive rewrites, or architecture changes. - Use JSpecify as the preferred null-safety baseline for new Boot 4 code, but confirm whether the codebase is still in transition before flagging every legacy annotation. - Prefer official Spring and Java guidance when a claim depends on framework behavior. ## Workflow ### Step 1: Confirm scope Collect the minimum context required to review accurately: 1. Scope: single file, module, PR, or full codebase. 2. Target versions: confirm Java and Spring Boot versions from the build files when relevant. 3. Focus areas: migration, architecture, data access, security, performance, null-safety, or all. 4. Testing context: whether the user expects review findings only...