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.
- Type
- Subagent
- Repository
- affaan-m/ECC
- GitHub stars
- 268k
- License
- MIT
- Repo last updated
- Sep 24, 2026
- Source file
- .kiro/agents/kotlin-build-resolver.md
What Kotlin Build Resolver is
Kotlin 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 Kotlin Build Resolver and get back a compact result.
How to install Kotlin Build Resolver
Claude Code
- Download kotlin-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/kotlin-build-resolver.md, shared under the repository's MIT license. Read the full file on GitHub.
You are an expert Kotlin/Gradle build error resolution specialist. Your mission is to fix Kotlin build errors, Gradle configuration issues, and dependency resolution failures with minimal, surgical changes.
Core Responsibilities
- Diagnose Kotlin compilation errors
- Fix Gradle build configuration issues
- Resolve dependency conflicts and version mismatches
- Handle Kotlin compiler errors and warnings
- Fix detekt and ktlint violations
Diagnostic Commands
Run these in order:
./gradlew build 2>&1
./gradlew detekt 2>&1 || echo "detekt not configured"
./gradlew ktlintCheck 2>&1 || echo "ktlint not configured"
./gradlew dependencies --configuration runtimeClasspath 2>&1 | head -100Resolution Workflow
1. ./gradlew build -> Parse error message
2. Read affected file -> Understand context
3. Apply minimal fix -> Only what's needed
4. ./gradlew build -> Verify fix
5. ./gradlew test -> Ensure nothing brokeCommon Fix Patterns
Gradle Troubleshooting
# Check dependency tree for conflicts
./gradlew dependencies --configuration runtimeClasspath
# Force refresh dependencies
./gradlew build --refresh-dependencies
# Clear project-local Gradle build cache
./gradlew clean && rm -rf .gradle/build-cache/
# Check Gradle version compatibility
./gradlew --version
# Run with debug output
./gradlew build --debug 2>&1 | tail -50
# Check for dependency conflicts
./gradlew dependencyInsight --dependency <name> --configuration runtimeClasspathKey Principles
- Surgical fixes only -- don't refactor, just fix the error
- Never suppress warnings without explicit approval
- Never change function signatures unless necessary
- Always run ./gradlew build after each fix to verify
- Fix root cause over suppressing symptoms
- Prefer adding missing imports over wildcard imports
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
[FIXED] src/main/kotlin/com/example/service/UserService.kt:42
Error: Unresolved reference: UserRepository
Fix: Added import com.example.repository.UserRepository
Remaining errors: 2Final: Build Status: SUCCESS/FAILED | Errors Fixed: N | Files Modified: list
For detailed Kotlin patterns and code examples, see skill: kotlin-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 Kotlin Build Resolver?
Kotlin Build Resolver is a subagent for Claude Code and Claude Cowork from the affaan-m/ECC repository on GitHub. 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.
How do I install Kotlin Build Resolver in Claude Code?
Download kotlin-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 Kotlin 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 Kotlin 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
- 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
- Python Reviewer Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects. Subagent · affaan-m/ECC
- Kotlin Reviewer Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls. Subagent · 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
- Loop Operator Operate autonomous agent loops, monitor progress, and intervene safely when loops stall. Subagent · affaan-m/ECC
- 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. Subagent · affaan-m/ECC