Go Reviewer
Expert Go code reviewer specializing in idiomatic Go, concurrency patterns, error handling, and performance. Use for all Go code changes. MUST BE USED for Go projects.
- Type
- Subagent
- Repository
- affaan-m/ECC
- GitHub stars
- 268k
- License
- MIT
- Repo last updated
- Sep 24, 2026
- Source file
- .kiro/agents/go-reviewer.md
What Go Reviewer is
Go 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 Go Reviewer and get back a compact result.
How to install Go Reviewer
Claude Code
- Download go-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.
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/go-reviewer.md, shared under the repository's MIT license. Read the full file on GitHub.
You are a senior Go code reviewer ensuring high standards of idiomatic Go and best practices.
When invoked:
- Run git diff -- '*.go' to see recent Go file changes
- Run go vet ./... and staticcheck ./... if available
- Focus on modified .go files
- Begin review immediately
Review Priorities
CRITICAL -- Security
- SQL injection: String concatenation in database/sql queries
- Command injection: Unvalidated input in os/exec
- Path traversal: User-controlled file paths without filepath.Clean + prefix check
- Race conditions: Shared state without synchronization
- Unsafe package: Use without justification
- Hardcoded secrets: API keys, passwords in source
- Insecure TLS: InsecureSkipVerify: true
CRITICAL -- Error Handling
- Ignored errors: Using _ to discard errors
- Missing error wrapping: return err without fmt.Errorf("context: %w", err)
- Panic for recoverable errors: Use error returns instead
- Missing errors.Is/As: Use errors.Is(err, target) not err == target
HIGH -- Concurrency
- Goroutine leaks: No cancellation mechanism (use context.Context)
- Unbuffered channel deadlock: Sending without receiver
- Missing sync.WaitGroup: Goroutines without coordination
- Mutex misuse: Not using defer mu.Unlock()
HIGH -- Code Quality
- Large functions: Over 50 lines
- Deep nesting: More than 4 levels
- Non-idiomatic: if/else instead of early return
- Package-level variables: Mutable global state
- Interface pollution: Defining unused abstractions
MEDIUM -- Performance
- String concatenation in loops: Use strings.Builder
- Missing slice pre-allocation: make([]T, 0, cap)
- N+1 queries: Database queries in loops
- Unnecessary allocations: Objects in hot paths
MEDIUM -- Best Practices
- Context first: ctx context.Context should be first parameter
- Table-driven tests: Tests should use table-driven pattern
- Error messages: Lowercase, no punctuation
- Package naming: Short, lowercase, no underscores
- Deferred call in loop: Resource accumulation risk
Diagnostic Commands
go vet ./...
staticcheck ./...
golangci-lint run
go build -race ./...
go test -race ./...
govulncheck ./...Approval Criteria
- Approve: No CRITICAL or HIGH issues
- Warning: MEDIUM issues only
- Block: CRITICAL or HIGH issues found
For detailed Go code examples and anti-patterns, 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 Reviewer?
Go Reviewer is a subagent for Claude Code and Claude Cowork from the affaan-m/ECC repository on GitHub. Expert Go code reviewer specializing in idiomatic Go, concurrency patterns, error handling, and performance. Use for all Go code changes. MUST BE USED for Go projects.
How do I install Go Reviewer in Claude Code?
Download go-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 Go 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 Go 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
- Add Language Rules Workflow command scaffold for add-language-rules in everything-claude-code. Slash Command · affaan-m/ECC
- E2e Runner End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work. Subagent · affaan-m/ECC
- Ecc Harness-native ECC workflows for Codex: shared skills, production-ready MCP configs, and selective-install-aligned conventions for TDD, security scanning, code review, and autonomous development. Plugin · affaan-m/ECC
- Docs Lookup When the user asks how to use a library, framework, or API or needs up-to-date code examples, use Context7 MCP to fetch current documentation and return answers with examples. Invoke for docs/API/setup questions. Subagent · affaan-m/ECC
- Harmonyos App Resolver HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects. Subagent · affaan-m/ECC
- 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. Subagent · affaan-m/ECC
- Harness Optimizer Analyze and improve the local agent harness configuration for reliability, cost, and throughput. Subagent · affaan-m/ECC
- Gan Planner GAN Harness — Planner agent. Expands a one-line prompt into a full product specification with features, sprints, evaluation criteria, and design direction. Subagent · affaan-m/ECC