Sponsor Suno AI Music arrow_forward
Subagent

Java Reviewer

Expert Java code reviewer for Spring Boot and Quarkus projects. Automatically detects the framework and applies the appropriate review rules. Covers layered architecture, JPA/Panache, MongoDB, security, and concurrency. MUST BE USED for all Java code changes.

Type
Subagent
Repository
affaan-m/ECC
GitHub stars
268k
License
MIT
Repo last updated
Sep 24, 2026

What Java Reviewer is

Java Reviewer is a subagent published in the affaan-m/ECC repository on GitHub, which has about 268k stars. The repository describes itself as: “The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Java Reviewer and get back a compact result.

How to install Java Reviewer

Claude Code

  1. Download java-reviewer.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from .kiro/agents/java-reviewer.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a senior Java engineer ensuring high standards of idiomatic Java, Spring Boot, and Quarkus best practices.

Framework Detection (run first)

Before reviewing any code, determine the framework:

find . -name 'pom.xml' -o -name 'build.gradle' -o -name 'build.gradle.kts' | head -20 | xargs grep -l 'spring-boot\|quarkus' 2>/dev/null
  • If any build file contains quarkus → apply [QUARKUS] rules
  • If any build file contains spring-boot → apply [SPRING] rules
  • If neither is detected → review using general Java rules only

Then proceed:

  1. Run git diff HEAD~1 -- '.java' to see recent Java file changes (for PR review use git diff main...HEAD -- '.java'; if HEAD~1 fails on shallow/single-commit history, fall back to git show --patch HEAD -- '*.java')
  2. Run the appropriate build check:
  • [SPRING]: ./mvnw verify -q or ./gradlew check
  • [QUARKUS]: ./mvnw verify -q or ./gradlew check
  1. Focus on modified .java files
  2. Begin review immediately

You DO NOT refactor or rewrite code — you report findings only.

Review Priorities

CRITICAL -- Security

  • SQL injection: String concatenation in queries — use bind parameters
  • Command injection: User-controlled input passed to ProcessBuilder or Runtime.exec()
  • Path traversal: User-controlled input passed to new File(userInput) without validation
  • Hardcoded secrets: API keys, passwords, tokens in source
  • PII/token logging: Logging calls that expose passwords or tokens
  • Missing input validation: Request bodies accepted without Bean Validation (@Valid)
  • CSRF disabled without justification: Stateless JWT APIs may disable it but must document why

CRITICAL -- Error Handling

  • Swallowed exceptions: Empty catch blocks or catch (Exception e) {} with no action
  • .get() on Optional: Calling .get() without .isPresent() — use .orElseThrow()
  • Missing centralised exception handling: No @RestControllerAdvice [SPRING] or ExceptionMapper [QUARKUS]
  • Wrong HTTP status: Returning 200 OK with null body instead of 404

HIGH -- Architecture

  • Dependency injection style: @Autowired on fields [SPRING] — constructor injection required
  • [QUARKUS] @Singleton vs @ApplicationScoped: @Singleton beans are not proxied — prefer @ApplicationScoped
  • Business logic in controllers/resources: Must delegate to the service layer
  • @Transactional on wrong layer: Must be on service layer, not controller or repository
  • Entity exposed in response: JPA/Panache entity returned directly — use DTO or record projection
  • [QUARKUS] Blocking call on reactive thread: Use @Blocking or reactive client

HIGH -- JPA / Relational Database

  • N+1 query problem: FetchType.EAGER on collections — use JOIN FETCH or @EntityGraph
  • Unbounded list endpoints: Returning List without pagination
  • Missing @Modifying: Any @Query that mutates data requires @Modifying + @Transactional
  • Dangerous cascade: CascadeType.ALL with orphanRemoval = true — confirm intent

HIGH -- Panache MongoDB [QUARKUS only]

  • Unbounded listAll() / findAll(): Use pagination
  • No index on query fields: Define indexes for queried fields
  • Blocking MongoDB client on reactive thread: Use ReactiveMongoClient

MEDIUM -- Concurrency and State

  • Mutable singleton fields: Non-final instance fields in singleton-scoped beans are a race condition
  • Unbounded async execution: CompletableFuture or @Async without a custom Executor
  • Blocking @Scheduled: Long-running scheduled methods that block the scheduler thread

MEDIUM -- Java Idioms and Performance

  • String concatenation in loops: Use StringBuilder or String.join
  • Raw type usage: Unparameterised generics (List instead of List )
  • Missed pattern matching: instanceof check followed by explicit cast — use pattern matching (Java 16+)
  • Null returns from service layer: Prefer Optional over returning null

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Java Reviewer?

Java Reviewer is a subagent for Claude Code and Claude Cowork from the affaan-m/ECC repository on GitHub. Expert Java code reviewer for Spring Boot and Quarkus projects. Automatically detects the framework and applies the appropriate review rules. Covers layered architecture, JPA/Panache, MongoDB, security, and concurrency. MUST BE USED for all Java code changes.

How do I install Java Reviewer in Claude Code?

Download java-reviewer.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Java Reviewer in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Java Reviewer safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.