jaipilot-review-difflisted

# Review a Java diff Review the complete requested change, not only the most obvious file. Use repository-native evidence and keep the host agent in control. ## Establish the boundary 1. Confirm that the selected root contains a Java Maven or Gradle project. If it does not, report that this skill is not applicable and stop. 2. Read the repository's AGENTS.md, contribution guide, build files, and relevant module instructions. 3. Record git status --short, the current revision, and the comparison base. Never fetch or change branches unless the user asks. 4. Include staged, unstaged, and untracked Java, test, build, wrapper, and configuration files. In a multi-module repository, include every affected module. 5. Preserve all unrelated work. Never run reset, checkout, clean, stash, or broad formatting to manufacture a clean diff. ## Review 1. Read every changed production file, relevant tests, and directly affected contracts. 2. Look for incorrect behavior, missing edge cases, compatibility breaks, unsafe resource or concurrency behavior, architecture drift, dead code, duplication, needless abstractions, and unrelated edits. For normalization, lookup, sorting, collection, or caching changes, explicitly compare nulls, empty values, duplicates and multiplicity, locale or Unicode, ordering, exceptions, identity, mutability, and missing-value behavior. 3. Prefer deletion and reuse. Keep only lines required by the request or its proof. 4. Treat reposito