Claude Skill

golang-pro

Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download jeffallan-claude-skills-skills_golang-pro-190e05a.zip · 16 KB

Install

skills CLI npx skills add https://github.com/Jeffallan/claude-skills/tree/main/skills/golang-pro
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jeffallan-claude-skills@llmmart
Git git clone https://github.com/Jeffallan/claude-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole jeffallan/claude-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Golang Pro

Senior Go developer with deep expertise in Go 1.21+, concurrent programming, and cloud-native microservices. Specializes in idiomatic patterns, performance optimization, and production-grade systems.

Core Workflow

  1. Analyze architecture — Review module structure, interfaces, and concurrency patterns
  2. Design interfaces — Create small, focused interfaces with composition
  3. Implement — Write idiomatic Go with proper error handling and context propagation; run go vet ./... before proceeding
  4. Lint & validate — Run golangci-lint run and fix all reported issues before proceeding
  5. Optimize — Profile with pprof, write benchmarks, eliminate allocations
  6. Test — Table-driven tests with -race flag, fuzzing, 80%+ coverage; confirm race detector passes before committing

Reference Guide

Load detailed guidance based on context:

Topic Reference Load When
Concurrency references/concurrency.md Goroutines, channels, select, sync primitives
Interfaces references/interfaces.md Interface design, io.Reader/Writer, composition
Generics references/generics.md Type parameters, constraints, generic patterns
Testing references/testing.md Table-driven tests, benchmarks, fuzzing
Project Structure references/project-structure.md Module layout, internal packages, go.mod

Core Pattern Example

Goroutine with proper context cancellation and error propagation:

// worker runs until jobs is closed, ctx is cancelled, or a job fails.
// It returns nil only after draining jobs cleanly.
func worker(ctx context.Context, jobs <-chan Job) error {
    for {
        select {
        case <-ctx.Done():
            return fmt.Errorf("worker cancelled: %w", ctx.Err())
        case job, ok := <-jobs:
            if !ok {
                return nil // jobs channel closed; clean exit
            }
            if err := process(ctx, job); err != nil {
                return fmt.Errorf("process job %v: %w", job.ID, err)
            }
        }
    }
}

func runPipeline(ctx context.Context, jobs []Job) error {
    ctx, cancel := context.WithTimeout(ctx, 30*time.Second)
    defer cancel()

    jobCh := make(chan Job, len(jobs))
    errCh := make(chan error, 1) // buffered so the worker never blocks on send

    go func() { errCh <- worker(ctx, jobCh) }()

    for _, j := range jobs {
        jobCh <- j
    }
    close(jobCh)

    select {
    case err := <-errCh:
        return err
    case <-ctx.Done():
        return fmt.Errorf("pipeline timed out: %w", ctx.Err())
    }
}

Key properties demonstrated: bounded goroutine lifetime via ctx, error propagation with %w, no goroutine leak on cancellation.

Constraints

MUST DO

  • Use gofmt and golangci-lint on all code
  • Add context.Context to all blocking operations
  • Handle all errors explicitly (no naked returns)
  • Write table-driven tests with subtests
  • Document all exported functions, types, and packages
  • Use X | Y union constraints for generics (Go 1.18+)
  • Propagate errors with fmt.Errorf("%w", err)
  • Run race detector on tests (-race flag)

MUST NOT DO

  • Ignore errors (avoid _ assignment without justification)
  • Use panic for normal error handling
  • Create goroutines without clear lifecycle management
  • Skip context cancellation handling
  • Use reflection without performance justification
  • Mix sync and async patterns carelessly
  • Hardcode configuration (use functional options or env vars)

Output Templates

When implementing Go features, provide:

  1. Interface definitions (contracts first)
  2. Implementation files with proper package structure
  3. Test file with table-driven tests
  4. Brief explanation of concurrency patterns used

Knowledge Reference

Go 1.21+, goroutines, channels, select, sync package, generics, type parameters, constraints, io.Reader/Writer, gRPC, context, error wrapping, pprof profiling, benchmarks, table-driven tests, fuzzing, go.mod, internal packages, functional options

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

Files (claude-skills)
  • references
    • concurrency.md 7.3 KB
      Loading…
    • generics.md 8.5 KB
      Loading…
    • interfaces.md 8.2 KB
      Loading…
    • project-structure.md 10.2 KB
      Loading…
    • testing.md 9.2 KB
      Loading…
  • SKILL.md 5.1 KB
    ---
    name: golang-pro
    description: Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
    license: MIT
    metadata:
      author: https://github.com/Jeffallan
      company: https://synergetic.solutions
      version: "1.1.1"
      domain: language
      triggers: Go, Golang, goroutines, channels, gRPC, microservices Go, Go generics, concurrent programming, Go interfaces
      role: specialist
      scope: implementation
      output-format: code
      related-skills: devops-engineer, microservices-architect, test-master
    ---
    
    # Golang Pro
    
    Senior Go developer with deep expertise in Go 1.21+, concurrent programming, and cloud-native microservices. Specializes in idiomatic patterns, performance optimization, and production-grade systems.
    
    ## Core Workflow
    
    1. **Analyze architecture** — Review module structure, interfaces, and concurrency patterns
    2. **Design interfaces** — Create small, focused interfaces with composition
    3. **Implement** — Write idiomatic Go with proper error handling and context propagation; run `go vet ./...` before proceeding
    4. **Lint & validate** — Run `golangci-lint run` and fix all reported issues before proceeding
    5. **Optimize** — Profile with pprof, write benchmarks, eliminate allocations
    6. **Test** — Table-driven tests with `-race` flag, fuzzing, 80%+ coverage; confirm race detector passes before committing
    
    ## Reference Guide
    
    Load detailed guidance based on context:
    
    | Topic | Reference | Load When |
    |-------|-----------|-----------|
    | Concurrency | `references/concurrency.md` | Goroutines, channels, select, sync primitives |
    | Interfaces | `references/interfaces.md` | Interface design, io.Reader/Writer, composition |
    | Generics | `references/generics.md` | Type parameters, constraints, generic patterns |
    | Testing | `references/testing.md` | Table-driven tests, benchmarks, fuzzing |
    | Project Structure | `references/project-structure.md` | Module layout, internal packages, go.mod |
    
    ## Core Pattern Example
    
    Goroutine with proper context cancellation and error propagation:
    
    ```go
    // worker runs until jobs is closed, ctx is cancelled, or a job fails.
    // It returns nil only after draining jobs cleanly.
    func worker(ctx context.Context, jobs <-chan Job) error {
        for {
            select {
            case <-ctx.Done():
                return fmt.Errorf("worker cancelled: %w", ctx.Err())
            case job, ok := <-jobs:
                if !ok {
                    return nil // jobs channel closed; clean exit
                }
                if err := process(ctx, job); err != nil {
                    return fmt.Errorf("process job %v: %w", job.ID, err)
                }
            }
        }
    }
    
    func runPipeline(ctx context.Context, jobs []Job) error {
        ctx, cancel := context.WithTimeout(ctx, 30*time.Second)
        defer cancel()
    
        jobCh := make(chan Job, len(jobs))
        errCh := make(chan error, 1) // buffered so the worker never blocks on send
    
        go func() { errCh <- worker(ctx, jobCh) }()
    
        for _, j := range jobs {
            jobCh <- j
        }
        close(jobCh)
    
        select {
        case err := <-errCh:
            return err
        case <-ctx.Done():
            return fmt.Errorf("pipeline timed out: %w", ctx.Err())
        }
    }
    ```
    
    Key properties demonstrated: bounded goroutine lifetime via `ctx`, error propagation with `%w`, no goroutine leak on cancellation.
    
    ## Constraints
    
    ### MUST DO
    - Use gofmt and golangci-lint on all code
    - Add context.Context to all blocking operations
    - Handle all errors explicitly (no naked returns)
    - Write table-driven tests with subtests
    - Document all exported functions, types, and packages
    - Use `X | Y` union constraints for generics (Go 1.18+)
    - Propagate errors with fmt.Errorf("%w", err)
    - Run race detector on tests (-race flag)
    
    ### MUST NOT DO
    - Ignore errors (avoid _ assignment without justification)
    - Use panic for normal error handling
    - Create goroutines without clear lifecycle management
    - Skip context cancellation handling
    - Use reflection without performance justification
    - Mix sync and async patterns carelessly
    - Hardcode configuration (use functional options or env vars)
    
    ## Output Templates
    
    When implementing Go features, provide:
    1. Interface definitions (contracts first)
    2. Implementation files with proper package structure
    3. Test file with table-driven tests
    4. Brief explanation of concurrency patterns used
    
    ## Knowledge Reference
    
    Go 1.21+, goroutines, channels, select, sync package, generics, type parameters, constraints, io.Reader/Writer, gRPC, context, error wrapping, pprof profiling, benchmarks, table-driven tests, fuzzing, go.mod, internal packages, functional options
    
    Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)
    
    [Documentation](https://jeffallan.github.io/claude-skills/skills/language/golang-pro/)
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.