Git History Bug Audit
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests.
Install Java Code Review
$ npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sivaprasadreddy/sivalabs-agent-skills java-code-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/java-code-review .claude/skills/java-code-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "java-code-review" agent skill from https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-review into .claude/skills/java-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-code-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sivaprasadreddy/sivalabs-agent-skills java-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/java-code-review .agents/skills/java-code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "java-code-review" agent skill from https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-review into .agents/skills/java-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-code-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sivaprasadreddy/sivalabs-agent-skills java-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/java-code-review .cursor/skills/java-code-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "java-code-review" agent skill from https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-review into .cursor/skills/java-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-code-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sivaprasadreddy/sivalabs-agent-skills.git --path skills/java-code-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sivaprasadreddy/sivalabs-agent-skills java-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/java-code-review .gemini/skills/java-code-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "java-code-review" agent skill from https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-review into .gemini/skills/java-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-code-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sivaprasadreddy/sivalabs-agent-skills java-code-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/java-code-review .github/skills/java-code-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "java-code-review" agent skill from https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-review into .github/skills/java-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-code-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sivaprasadreddy/sivalabs-agent-skills java-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/java-code-review .opencode/skills/java-code-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "java-code-review" agent skill from https://github.com/sivaprasadreddy/sivalabs-agent-skills/tree/main/skills/java-code-review into .opencode/skills/java-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-code-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
java-code-review- GitHub stars
- 188
- Token cost
- ~1.2k tokens
- SKILL.md length
- 520 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests.
- Works in 4 steps: If the user explicitly specifies files,… → Otherwise inspect the git worktree and… → Include only Java and Java-adjacent… → …
- Explicitly names files
- SKILL.md covers Establish the review scope, Review for, Validate findings and Write review.md, plus 1 more section
- Calls git
What it does
Java Code Review is an agent skill from sivaprasadreddy/sivalabs-agent-skills. Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review. It works with Java and Git. The repository describes itself as: Spring Boot skills for AI coding agents. The licence is MIT.
When your agent uses it
- Explicitly names files
- Review that scope instead
Example prompts
- “/java-code-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- If the user explicitly specifies files, classes, packages, commits, or a
- Otherwise inspect the git worktree and review modified, added, or renamed
- Include only Java and Java-adjacent files relevant to behavior (for
- Read enough surrounding code, callers, tests, configuration, and interfaces
What it can do on your machine
Read from SKILL.md and the folder at commit e9f9861. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Java Code Review loads about 1.2k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 520 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sivaprasadreddy/sivalabs-agent-skills at commit e9f9861, republished under its MIT licence (© sivaprasadreddy). 520 words, ~1,210 tokens.
Download SKILL.mdSave it as
.claude/skills/java-code-review/SKILL.md (or your agent's skills folder).- name
- java-code-review
- description
- Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.
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
- If the user explicitly specifies files, classes, packages, commits, or a diff, use that scope and do not silently broaden it.
- Otherwise inspect the git worktree and review modified, added, or renamed
files. Use
git status --shortand the relevantgit diff(including staged changes when present). For renamed files, review the resulting file and the meaningful diff. - 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.
- 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 reduce meaningful drift.
- Needs improvement: unclear or brittle design, excessive coupling, misleading names, avoidable complexity, test gaps, performance concerns, and violations of established project conventions.
Prioritize correctness and impact over style. Do not flag formatting or an opinionated alternative unless it creates a concrete maintenance, reliability, security, or performance problem. Distinguish confirmed issues from risks or questions, and avoid speculative findings.
Validate findings
For every finding, trace the relevant control flow and data flow. Check nearby tests and, when practical, run the narrowest useful test, compile, static analysis, or reproduction command. Do not change files to make validation pass. If validation cannot be run, say why. Check whether a suspected issue is already handled by a caller, framework contract, annotation, or configuration.
Show full SKILL.md (188 more words)Show less
Write review.md
Before writing, check whether the requested output file already exists.
- If it exists, ask the user whether to overwrite it or use a new filename; do not overwrite without that choice.
- If the user chooses a new filename, use exactly that filename (within the repository or requested output location).
- If no report exists, create
review.md.
The report must be self-contained and include:
# Java Code Review
## Scope
<!-- files/diff reviewed, review date, and validation performed -->
## Summary
<!-- concise overall assessment and finding counts by severity -->
## Findings
### [SEVERITY] Short title
- **Location:** `path/to/File.java:line`
- **Category:** Bug | Duplicate code | Improvement
- **Confidence:** High | Medium | Low
**Problem**
Explain the concrete behavior and why it matters, citing the relevant code.
**Suggested fix**
Give a specific implementation approach, including edge cases and tests to
add or update. Do not merely say “refactor” or “add validation.”
## Positive observations
<!-- optional; mention useful safeguards or clear design choices -->
## Validation
<!-- commands run and their outcomes, or why validation was unavailable -->Use severity consistently: Blocker (unsafe or clearly broken), High (likely production failure or serious security/data issue), Medium (meaningful bug or maintainability risk), and Low (minor but actionable). Order findings by severity, then by file and line. Include one finding per distinct problem, avoid duplicates, and use precise line references that still make sense in the reviewed version. If no findings are found, say so clearly and still include scope, validation, and positive observations.
Final response
Tell the user that the report was created and link to the generated file. Give the finding count and briefly call out any Blocker or High findings. If the report could not be created because an existing file needs a choice, ask the overwrite/new-filename question and stop before writing.
© sivaprasadreddy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/java-code-review of sivaprasadreddy/sivalabs-agent-skills.
Open the folder on GitHubat commit e9f9861
Compare with similar skills
Java Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Java Code Review this skillsivaprasadreddy/sivalabs-agent-skills | 188 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Git History Bug Auditben-manes/caffeine | 18k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Parallel Adversarial Change Reviewben-manes/caffeine | 18k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Open Code Review CLIalibaba/open-code-review | 44k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Parallel Adversarial Change Review
ben-manes/caffeine
Runs three parallel reviewers on a diff or branch, one blind, one design-aware and one matching past bug patterns, then triages their findings.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
Hunk Diff Session Control
modem-dev/hunk
Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline…
More from sivaprasadreddy/sivalabs-agent-skills
Jspecify Skill
sivaprasadreddy/sivalabs-agent-skills
A skill your agent uses when asked to perform any of the following actions in a Java project: - To add jspecify support - To prevent NullPointerExceptions - To better handle Nullability This skill…
Apply Renovate PRs
sivaprasadreddy/sivalabs-agent-skills
Apply the changes from all open Renovate bot pull requests of a GitHub repository into the local working tree.
Progen
sivaprasadreddy/sivalabs-agent-skills
A skill your agent uses when the user wants to create/generate/scaffold a new Spring Boot project (Maven or Gradle, REST API / Web App / Spring Boot + Angular full stack).
Spring Modulith Verifier
sivaprasadreddy/sivalabs-agent-skills
Verifies whether code follows Spring Modulith code structure or not.
Spring Boot Skill
sivaprasadreddy/sivalabs-agent-skills
Build Spring Boot 4.x applications following the best practices.
Related
Categories
Questions about Java Code Review
What does Java Code Review do?
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. Java Code Review is an agent skill from sivaprasadreddy/sivalabs-agent-skills. Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests.
When should I use Java Code Review?
Java Code Review fits situations like: explicitly names files; review that scope instead.
How do I install Java Code Review in Claude Code?
Run `npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a claude-code`. Or copy the skill folder (skills/java-code-review in sivaprasadreddy/sivalabs-agent-skills) into .claude/skills/java-code-review in your project. Claude Code loads it when a task matches its description.
How do I install Java Code Review in Codex?
Run `npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a codex`. Or copy the skill folder (skills/java-code-review in sivaprasadreddy/sivalabs-agent-skills) into .agents/skills/java-code-review in your project. Codex loads it when a task matches its description.
Can I use Java Code Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sivaprasadreddy/sivalabs-agent-skills --skill java-code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/java-code-review, .gemini/skills/java-code-review, .github/skills/java-code-review and .opencode/skills/java-code-review in your project.
What does Java Code Review need to run?
Going by SKILL.md and its folder, Java Code Review needs the command-line tools its instructions call (git).
Does Java Code Review access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Java Code Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Java Code Review use?
Java Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Java Code Review use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Java Code Review?
Skills that share tags, products or a category with Java Code Review: Git History Bug Audit (ben-manes/caffeine, 18k stars), Parallel Adversarial Change Review (ben-manes/caffeine, 18k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Java Code Review?
sivaprasadreddy (a GitHub user) maintains it in sivaprasadreddy/sivalabs-agent-skills, which has 188 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.
Source: sivaprasadreddy/sivalabs-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.