BUILD AND RUNTIME DIAGNOSTICS / Affaan Mustafa
Go build error resolver
Resolves Go compiler, module, vet and linter failures while keeping changes bounded to the reported build problem.
“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.”
01 / THE REASONING
Why this made the selection.
- The workflow checks compilation before narrowing into interfaces, imports, cycles and module resolution.
- It requests verification after each change and stops when the same error persists across three attempts.
- It fixes build, vet, and linter failures with Write and Edit allowed, and it requires go mod tidy after import changes.
- It forbids //nolint and signature changes without necessity, and it stops when the same error survives three tries or the fix needs an architectural change.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- agents/go-build-resolver.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable
Our findings
- The workflow checks compilation before narrowing into interfaces, imports, cycles and module resolution.
- It requests verification after each change and stops when the same error persists across three attempts.
- Tools include Write, Edit, and Bash, and the mission is a surgical fix rather than a review comment.
- The module section shows go get at a pinned version and a modcache clean followed by go mod download.
- Stop rules bar a third repeat of the same error and architectural rewrites. //nolint requires explicit approval.
- Copying the file into ~/.claude/agents/ is a separate step in the pinned README. The file does not register itself.
Not established by this review
- No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Use the role in your project.
- Read the pinned definition and MIT licence; review the host permissions before use.
- Inspect the complete upstream context, place the agent in .claude/agents/ and limit edits/commands to a disposable checkout and the failing target.
- Provide the failing package/workspace, exact compiler output and go.mod/go.sum context.
Before you start
- Claude Code and a supported model
- The project-specific Go toolchain, dependencies and a reproducible failure
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/agents/go-build-resolver.md
Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/LICENSE
Supports: Licence and attribution requirements
https://code.claude.com/docs/en/sub-agents.md
Supports: Host setup and permission defaults