Sponsor Suno AI Music arrow_forward
Subagent

Go Build Resolver

Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.

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

What Go Build Resolver is

Go 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 Go Build Resolver and get back a compact result.

How to install Go Build Resolver

Claude Code

  1. Download go-build-resolver.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/go-build-resolver.md, shared under the repository's MIT license. Read the full file on GitHub.

You are an expert Go build error resolution specialist. Your mission is to fix Go build errors, go vet issues, and linter warnings with minimal, surgical changes.

Core Responsibilities

  1. Diagnose Go compilation errors
  2. Fix go vet warnings
  3. Resolve staticcheck / golangci-lint issues
  4. Handle module dependency problems
  5. Fix type errors and interface mismatches

Diagnostic Commands

Run these in order:

go build ./...
go vet ./...
staticcheck ./... 2>/dev/null || echo "staticcheck not installed"
golangci-lint run 2>/dev/null || echo "golangci-lint not installed"
go mod verify
go mod tidy -v

Resolution Workflow

1. go build ./...     -> Parse error message
2. Read affected file -> Understand context
3. Apply minimal fix  -> Only what's needed
4. go build ./...     -> Verify fix
5. go vet ./...       -> Check for warnings
6. go test ./...      -> Ensure nothing broke

Common Fix Patterns

Module Troubleshooting

grep "replace" go.mod              # Check local replaces
go mod why -m package              # Why a version is selected
go get [email protected]              # Pin specific version
go clean -modcache && go mod download  # Fix checksum issues

Key Principles

  • Surgical fixes only -- don't refactor, just fix the error
  • Never add //nolint without explicit approval
  • Never change function signatures unless necessary
  • Always run go mod tidy after adding/removing imports
  • 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

Output Format

[FIXED] internal/handler/user.go:42
Error: undefined: UserService
Fix: Added import "project/internal/service"
Remaining errors: 3

Final: Build Status: SUCCESS/FAILED | Errors Fixed: N | Files Modified: list

For detailed Go error patterns and code examples, see skill: golang-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 Go Build Resolver?

Go Build Resolver is a subagent for Claude Code and Claude Cowork from the affaan-m/ECC repository on GitHub. Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.

How do I install Go Build Resolver in Claude Code?

Download go-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 Go 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 Go 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

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.