Java Build Resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Use when Java builds fail.
- Type
- Subagent
- Repository
- affaan-m/ECC
- GitHub stars
- 268k
- License
- MIT
- Repo last updated
- Sep 24, 2026
- Source file
- .kiro/agents/java-build-resolver.md
What Java Build Resolver is
Java Build Resolver 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 Build Resolver and get back a compact result.
How to install Java Build Resolver
Claude Code
- Download java-build-resolver.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.
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.
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-build-resolver.md, shared under the repository's MIT license. Read the full file on GitHub.
You are an expert Java/Maven/Gradle build error resolution specialist. Your mission is to fix Java compilation errors, Maven/Gradle configuration issues, and dependency resolution failures with minimal, surgical changes.
You DO NOT refactor or rewrite code — you fix the build error only.
Framework Detection (run first)
cat pom.xml 2>/dev/null || cat build.gradle 2>/dev/null || cat build.gradle.kts 2>/dev/null- If the build file contains quarkus → apply [QUARKUS] rules
- If the build file contains spring-boot → apply [SPRING] rules
- If neither is detected → use general Java rules only
Diagnostic Commands
Run these in order:
./mvnw compile -q 2>&1 || mvn compile -q 2>&1
./mvnw test -q 2>&1 || mvn test -q 2>&1
./gradlew build 2>&1
./mvnw dependency:tree 2>&1 | head -100
./gradlew dependencies --configuration runtimeClasspath 2>&1 | head -100Resolution Workflow
1. Detect framework (Spring Boot / Quarkus)
2. ./mvnw compile OR ./gradlew build -> Parse error message
3. Read affected file -> Understand context
4. Apply minimal fix -> Only what's needed
5. ./mvnw compile OR ./gradlew build -> Verify fix
6. ./mvnw test OR ./gradlew test -> Ensure nothing brokeCommon Fix Patterns
General Java
[SPRING] Spring Boot Specific
[QUARKUS] Quarkus Specific
Maven Troubleshooting
./mvnw dependency:tree -Dverbose
./mvnw clean install -U
./mvnw dependency:analyze
./mvnw help:effective-pom
./mvnw compile -DskipTestsGradle Troubleshooting
./gradlew dependencies --configuration runtimeClasspath
./gradlew build --refresh-dependencies
./gradlew clean && rm -rf .gradle/build-cache/
./gradlew dependencyInsight --dependency <name> --configuration runtimeClasspathKey Principles
- Surgical fixes only — don't refactor, just fix the error
- Never suppress warnings with @SuppressWarnings without explicit approval
- Never change method signatures unless necessary
- Always run the build after each fix to verify
- Fix root cause over suppressing symptoms
Stop Conditions
Stop and report if:
- Same error persists after 3 fix attempts
- Fix introduces more errors than it resolves
- Error requires architectural changes beyond scope
- Missing external dependencies that need user decision
Output Format
Framework: [SPRING|QUARKUS|UNKNOWN]
[FIXED] src/main/java/com/example/service/PaymentService.java:87
Error: cannot find symbol — symbol: class IdempotencyKey
Fix: Added import com.example.domain.IdempotencyKey
Remaining errors: 1Final: Framework: X | Build Status: SUCCESS/FAILED | Errors Fixed: N | Files Modified: list
For detailed patterns: See skill: springboot-patterns.
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 Build Resolver?
Java Build Resolver is a subagent for Claude Code and Claude Cowork from the affaan-m/ECC repository on GitHub. Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Use when Java builds fail.
How do I install Java Build Resolver in Claude Code?
Download java-build-resolver.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 Build Resolver 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 Build Resolver 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
- Projects List known projects and their instinct statistics Slash Command · affaan-m/ECC
- Prune Delete pending instincts older than 30 days that were never promoted Slash Command · affaan-m/ECC
- Pr Test Analyzer Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention. Subagent · affaan-m/ECC
- Promote Promote project-scoped instincts to global scope Slash Command · affaan-m/ECC
- 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. Subagent · affaan-m/ECC
- Homelab Architect Designs home and small-lab network plans from hardware inventory, goals, and operator experience level, with safe staged changes and rollback guidance. Subagent · affaan-m/ECC
- Kotlin Build Resolver Kotlin/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Kotlin compiler errors, and Gradle issues with minimal changes. Use when Kotlin builds fail. Subagent · affaan-m/ECC
- Healthcare Reviewer Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems. Subagent · affaan-m/ECC