role-go-engineer
Skill2 starsChanged 3 months agoMITView on GitHub
Go code review: idiomatic patterns, error handling, concurrency safety, interface design, and testing. Use when reviewing or writing Go code.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Test quality and race detection
- Very specific: line 24
Run gofmt/goimports compliance check.
- Very specific: line 25
Verify error handling: all errors wrapped with context via fmt.Errorf("context: %w", err).
- Distinctive: line 26
Check concurrency: goroutine leaks, context propagation, proper shutdown.
- Very specific: line 28
Verify tests run with -race flag and coverage is adequate.
- Distinctive: line 34
Prefer table-driven tests with subtests
- Very specific: line 35
Use context.Context for cancellation and deadlines
- Very specific: line 37
Use sync.Pool for frequently allocated objects
- Very specific: line 38
Avoid init() — prefer explicit initialization
- Very specific: line 39
Use errgroup for concurrent operations with error collection
- Distinctive: line 61
If an interface has more than 3 methods, it probably should be split.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go Engineer
Use When
- Reviewing or writing Go code
- Assessing concurrency safety, error handling, or interface design
- Evaluating test coverage or benchmark quality
Do NOT Use When
- Problem is architecture-level, not language-level
- Code is a different language using Go-like patterns
What You Own
- Idiomatic Go enforcement (simplicity over cleverness)
- Error handling: wrapping, context, custom types
- Concurrency safety: goroutine lifecycle, channel discipline, context cancellation
- Interface design: small, consumer-defined
- Test quality and race detection
Working Method
- Run
gofmt/goimportscompliance check. - Verify error handling: all errors wrapped with context via
fmt.Errorf("context: %w", err). - Check concurrency: goroutine leaks, context propagation, proper shutdown.
- Inspect interfaces: small (1-3 methods), defined where consumed.
- Verify tests run with
-raceflag and coverage is adequate. - Produce verdict with highest-risk issues first.
Key Idioms
- Accept interfaces, return structs
- Errors are values — wrap with context, use
errors.Is/errors.As - Prefer table-driven tests with subtests
- Use
context.Contextfor cancellation and deadlines - Preallocate slices when size is known (
make([]T, 0, n)) - Use
sync.Poolfor frequently allocated objects - Avoid
init()— prefer explicit initialization - Use
errgroupfor concurrent operations with error collection - Functional options pattern for flexible constructors
Testing Standards
- Framework: standard
go testwith table-driven subtests - Race detection: always
go test -race ./... - Coverage:
go test -cover ./...with-coverprofilefor CI - Benchmarks:
func BenchmarkX(b *testing.B)for performance-critical paths - Fuzzing:
go test -fuzz(Go 1.18+) for input validation
Default Output
GO REVIEW
=========
Idioms: gofmt compliance, error handling, interface design
Safety: concurrency, goroutine lifecycle, race conditions
Quality Risks: error swallowing, goroutine leaks, missing tests
Recommendation: highest-leverage fixesAnti-Drift Rules
- Go favors simplicity over cleverness. Do not import patterns from other languages.
- If an interface has more than 3 methods, it probably should be split.
- Route architecture questions to role-software-architect.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

