# Jaipilot Review Diff

> Review and verify Java changes in Git using the repository's existing build, tests, coverage, mutation, architecture, and static-analysis tools. Use for Java diff review, pull-request review, pre-commit checks, changed-code risk, regression analysis, or requests to prove a Java change.

- **Type:** Skill
- **Install:** `agentstack add skill-jaipilot-jaipilot-jaipilot-review-diff`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [JAIPilot](https://agentstack.voostack.com/s/jaipilot)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [JAIPilot](https://github.com/JAIPilot)
- **Source:** https://github.com/JAIPilot/jaipilot/tree/main/plugins/jaipilot/skills/jaipilot-review-diff
- **Website:** https://github.com/JAIPilot/jaipilot#readme

## Install

```sh
agentstack add skill-jaipilot-jaipilot-jaipilot-review-diff
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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.
3. Prefer deletion and reuse. Keep only lines required by the request or its proof.
4. 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.
5. 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.
4. Confirm that changed tests actually executed. Do not infer test quality from a green build or
   line coverage alone.
5. Re-read the final diff after verification and check that generated output did not enter it.
6. 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](https://github.com/JAIPilot)
- **Source:** [JAIPilot/jaipilot](https://github.com/JAIPilot/jaipilot)
- **License:** MIT
- **Homepage:** https://github.com/JAIPilot/jaipilot#readme

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jaipilot-jaipilot-jaipilot-review-diff
- Seller: https://agentstack.voostack.com/s/jaipilot
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.