claude-code-java

Install

npx skills@latest add decebals/claude-code-java

This is third-party code. Review the repository files before installing.

What it does

Eighteen skills are grouped into workflow (commits, changelogs, issue triage), code quality (Java review, REST API contracts, thread safety, performance smells, tests, Maven dependencies, OWASP audits), architecture (package structure review, SOLID, patterns, clean code) and frameworks (Spring Boot, JPA, logging, Java version migration). The author tests that the agent picks the right skill from its description: eval-routing.sh runs a prompt set and reports misroutes. Beyond skills, the repository has a project setup script that generates CLAUDE.md, MCP configuration and Claude Code settings.

Who it is for. For Java developers on Maven or Gradle who work with Claude Code or another skills-aware agent.

Example request

Review this Spring Boot service for null safety, transactions and N+1 queries

Limitations

The skills target Java 11 and newer, with 17+ recommended. The routing check needs an OpenAI-compatible endpoint, which can be local. Setup scripts are shell-based.

How to disable. Delete the skill folders from the project's .claude/skills or the agent's directory.

Security check

• The skills consist of instructions and checklists

README in short

The README explains the set's purpose, the skill routing check and two install paths: npx skills or cloning and running setup-project.sh. It includes a grouped skill table with trigger phrases, the repository layout and requirements. It mentions the pairing with a GitHub Action for review. MIT licensed.

SKILL.md

---
name: java-code-review
description: Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.
license: MIT
---

# Java Code Review Skill

Systematic code review checklist for Java projects.

## When to Use
- User says "review this code" / "check this PR" / "code review"
- Before merging a PR
- After implementing a feature

## Review Strategy

1. **Quick scan** - Understand intent, identify scope
2. **Checklist pass** - Go through each category below
3. **Summary** - List findings by severity (Critical → Minor)

## Output Format

```markdown
## Code Review: [file/feature name]

### Critical
- [Issue description + line reference + suggestion]

### Improvements
- [Suggestion + rationale]

### Minor/Style
- [Nitpicks, optional improvements]

### Good Practices Observed
- [Positive feedback - important for morale]
```

---

## Review Checklist

### 1. Null Safety

Related