Use this skill when editing or reviewing Go code, focusing on idiomatic Go, package structure, error handling, concurrency, and testing.
Do not use for:
- Formal review or fix/debug workflows
- Operations risk assessment
- General change boundaries unrelated to Go
Core rules
- Keep implementations simple, explicit, and idiomatic.
- Prefer clear package boundaries and separation of responsibilities.
- Errors must be handled, and sufficient context must be preserved.
- Concurrency must consider lifecycle, cancellation, and data races.
- Tests should prioritize covering affected behavior.
Expand as needed
- Style:
references/style.md - Error handling:
references/errors.md - Concurrency:
references/concurrency.md - Testing:
references/testing.md - Project structure:
references/project-shape.md