Jaipilot Review Diff

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.

1. Read the repository's AGENTS.md, contribution guide, build files, and relevant module

instructions.

1. Record git status --short, the current revision, and the comparison base. Never fetch or change

branches unless the user asks.

1. Include staged, unstaged, and untracked Java, test, build, wrapper, and configuration files.

In a multi-module repository, include every affected module.

1. 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.

1. Prefer deletion and reuse. Keep only lines required by the request or its proof.
2. Treat repository-configured compiler checks, Checkstyle, PMD, SpotBugs, Error Prone, ArchUnit,

SonarQube reports, and similar tools as evidence. Do not invent equivalent findings when a tool is absent.

1. Make corrections only when the user asked for implementation. Otherwise report findings with

file, location, impact, and the smallest reasonable fix.

Verify

1. Use the repository wrapper and documented commands. Run focused tests while iterating.
2. Run the normal module or repository verification command after the diff stabilizes.
3. Run configured JaCoCo, PIT, ArchUnit, OpenRewrite, or static-analysis tasks when they apply.

Do not add plugins, dependencies, exclusions, suppressions, or weaker thresholds merely to pass.

1. Confirm that changed tests actually executed. Do not infer test quality from a green build or

line coverage alone.

1. Re-read the final diff after verification and check that generated output did not enter it.
2. If a command cannot run, report the exact failure and leave that property unavailable.

Report

Return:

• revision, comparison base, modules, and files reviewed;
• findings ordered by severity, followed by extra or unnecessary code;
• edits made and why each was necessary;
• exact commands and whether each passed, failed, skipped, or was unavailable;
• test execution, coverage, mutation, architecture, and analyzer evidence when measured; and
• residual risks and unverified boundaries.

Do not claim that the change is correct solely because the build passed.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: JAIPilot
• Source: JAIPilot/jaipilot
• License: MIT
• Homepage: https://github.com/JAIPilot/jaipilot#readme

Install and usage instructions live in the source repository linked above.