golang-development:review

A command that reviews Go source code, which is written in the Go programming language, for common mistakes and recommended coding patterns.

In plain words
What is it for?
Use it to review a Go file or directory for coding style, performance, security, concurrency, or error-handling problems, with suggestions for fixes.
Why use it?
It helps find unclear, slow, unsafe, or error-prone code before those problems reach users. You can review a whole project or focus on one area, such as security or concurrency, where multiple tasks run at once.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/geoffjay/claude-plugins/review
Clone the repo
git clone --depth 1 https://github.com/geoffjay/claude-plugins
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,376 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.02376
Opus 5 $0.00013 $0.01188
Sonnet 5 $0.00005 $0.00475
Haiku 4.5 $0.00003 $0.00238

Measured 2d ago against content hash 89d65c941e27, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

golang-development:review scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

data := fetch(url)
plugins/golang-development/commands/review.md · 444 lines

How it starts

The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Golang Development Review Command

Comprehensive Go code review focusing on idiomatic patterns, performance, security, and best practices.

Usage

/golang-development:review [file-path-or-directory] [focus-area]

Arguments

  • $1 - File path or directory to review (optional, defaults to current directory)
  • $2 - Focus area: all, idioms, performance, security, concurrency, errors (optional, defaults to all)

Examples

# Review all files in current directory
/golang-development:review

# Review specific file
/golang-development:review internal/service/user.go

# Focus on performance issues
/golang-development:review . performance

# Focus on security
/golang-development:review ./handlers security

# Review concurrency patterns
/golang-development:review . concurrency

Review Categories

1. Idiomatic Go (idioms)

Checks:

  • Naming conventions (camelCase, capitalization)
  • Error handling patterns
  • Interface usage and design
  • Struct composition over inheritance
  • Receiver naming and types
  • Exported vs. unexported identifiers
  • Go proverbs adherence

Example Issues:

// ❌ BAD: Non-idiomatic error handling
func getUser(id string) (*User, string) {
    if id == "" {
        return nil, "invalid ID"
    }
    // ...
}

// ✅ GOOD: Idiomatic error handling
func GetUser(id string) (*User, error) {
    if id == "" {
        return nil, fmt.Errorf("invalid ID: %s", id)
    }
    // ...
}

// ❌ BAD: Getter naming
func (u *User) GetName() string {
    return u.name
}

// ✅ GOOD: Idiomatic getter
func (u *User) Name() string {
    return u.name
}

// ❌ BAD: Setter without validation
func (u *User) SetAge(age int) {
    u.age = age
}

// ✅ GOOD: Validated setter with error
func (u *User) SetAge(age int) error {
    if age < 0 || age > 150 {
        return fmt.Errorf("invalid age: %d", age)
    }
    u.age = age
    return nil
}

2. Performance (performance)

Checks:

  • Unnecessary allocations
  • String concatenation in loops
  • Slice pre-allocation
  • Map pre-allocation
  • Defer in loops
  • Inefficient algorithms
  • Memory leaks
  • Goroutine leaks

Read the full file on GitHub · 444 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 444 lines · 26 tokens per session scan A 89d65c941e27

Subscribe to this mod's changes

golang-development:review is a command published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 26 tokens to every session and 2,376 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.