go-standards
Skill1 starsChanged 7 months agoMITView on GitHub
Go coding standards skill covering naming conventions, error handling, concurrency safety, database standards, and function design. Use when writing or reviewing Go code.
- Installs packages
3 other projects use a version of this.
Adopted by
Most recently taken up by
- llp-dev/claude-skillstheir own version, first seen Sep 9, 2026
- llp42/claude-skillstheir own version, first seen Sep 9, 2026
- motola10/claude-code-basetheir own version, first seen Jun 26, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- motola10/claude-code-base★ 1same name
- llp-dev/claude-skills★ 0same name
- llp42/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- review-standards/CLAUDE.mdCLAUDE.md
- frontend-standardsSkill
- review-standardsSkill
- security-standardsSkill
- testing-standardsSkill
- verifierSkill
The file
Files
Go Standards
Overview
Go coding standards organized into focused modules for precision and maintainability.
Modules
| Module | Description |
| Naming | camelCase, verb prefix, no magic values |
| Error Handling | errors.Is(), zero-value, wrapping |
| Concurrency | SafeGo, channels, goroutine leak prevention |
| Database | GORM explicit column tags, NOT NULL constraints |
| Function Design | Complexity ≤15, single responsibility |
| JSON Marshaling | No string concat, use struct marshal |
Core Principles (Summary)
| Principle | Canonical Location |
| Backend owns business logic | Database |
| SafeGo for goroutines | Concurrency |
| errors.Is() for error comparison | Error Handling |
| Zero-value pattern | Error Handling |
| GORM explicit column tags | Database |
| Cyclomatic complexity ≤15 | Function Design |
| No mock data, TODO/FIXME | Function Design |
| Struct marshal JSON | JSON Marshaling |
File Structure
go-standards/
├── SKILL.md # Main entry
├── naming.md # Naming conventions
├── error-handling.md # Error handling patterns
├── concurrency.md # Concurrency safety
├── database.md # GORM and database standards
├── function-design.md # Function design principles
└── json-marshaling.md # JSON serialization standardsDevelopment Commands
# Install golangci-lint
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
# Static analysis
go vet ./...
# Lint check (required before any PR)
golangci-lint run ./...
# Format code
gofmt -w .
goimports -w .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.