メニュー
Idiomatic Go style and best practices review. Use when checking interface design, pointer usage, or Go-specific idioms. Ensures code follows standard Go conventions and readability principles.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | golang-idiomatic-go |
| description | Idiomatic Go style and best practices review. Use when checking interface design, pointer usage, or Go-specific idioms. Ensures code follows standard Go conventions and readability principles. |
| license | MIT |
| metadata | {"author":"saifoelloh","version":"2.1.0","parent_skill":"golang-best-practices","sources":["Learning Go: An Idiomatic Approach (Jon Bodner)","Effective Go"],"last_updated":"2026-03-13"} |
Expert-level review for idiomatic Go patterns. Ensures code follows Go conventions, proper interface design, and appropriate pointer usage.
Use this skill when:
| Priority | Count | Focus |
|---|---|---|
| High | 1 | Method receivers |
| Medium | 5 | Go idioms and patterns |
high-pointer-receiver - Use pointer receivers for mutationsmedium-interface-pollution - Keep interfaces small (<5 methods)medium-accept-interface-return-struct - API flexibility patternmedium-pointer-overuse - Don't overuse pointers for small typesmedium-usecase-complexity - Move business logic to domain entitiesmedium-interface-in-implementation - Define interfaces where used// ✅ GOOD: Accept interface, return struct
func Process(r io.Reader) (*Result, error) {
// ...
return &Result{}, nil
}
// ✅ GOOD: Small, focused interface
type Reader interface {
Read(p []byte) (n int, err error)
}
// ✅ GOOD: Pointer receiver modifies state
func (u *User) UpdateEmail(email string) {
u.Email = email
}
This skill activates when you say:
## Idiomatic Go Improvements: X
### [Rule Name] (Line Y)
**Pattern**: Interface Design / Pointer Usage / Method Receiver
**Issue**: Violates Go idiom
**Fix**: Suggested correction
**Example**:
```go
// Idiomatic Go code
Based on "Learning Go" and Effective Go:
Comprehensive Go + GORM + PostgreSQL review meta-skill. Coordinates 9 specialized domain skills for fullstack Go application audits. Covers concurrency, architecture, idioms, queries, SQL performance, and migration safety.
Unified Go + GORM + PostgreSQL error handling review. Covers error wrapping, context propagation, PostgreSQL error codes (23505, 40001), errors.Is/As mapping, and retry logic. Ensures proper error chains and robust database failure recovery.
GORM ORM query pattern review for PostgreSQL. Use when reviewing or writing Go database code using GORM — covers N+1, Preload vs Joins, transactions, error checking, Save vs Updates, and context propagation. Trigger on any GORM method usage.
Database migration safety review for GORM + PostgreSQL. Use when writing or reviewing schema changes, AutoMigrate usage, ALTER TABLE statements, or index creation. Covers zero-downtime patterns, NOT NULL backfill, CONCURRENTLY indexes, idempotency, and rollback files.
PostgreSQL SQL syntax review for Go/GORM projects. Use when writing or reviewing raw SQL used via db.Raw(), db.Exec(), or migrations. Covers placeholder style, reserved keyword quoting, RETURNING, ILIKE, JSONB operators, and type casting. Don't use for MySQL or SQLite.
GORM + PostgreSQL query performance review. Use when optimizing slow queries, designing indexes, analyzing N+1 patterns, or configuring connection pools. Trigger on "slow", "optimize", "index", "EXPLAIN", "N+1", or performance degradation.