Go skills by samber

Install

npx skills add https://github.com/samber/cc-skills-golang --all

This is third-party code. Review the repository files before installing.

What it does

The set comes from the author of samber/lo and samber/do, distilled from his project commits and reworked by hand. General skills cover style and naming, error handling, safety, concurrency and context, databases, testing, benchmarks with pprof and benchstat, observability, modernizing for newer Go versions and safe refactoring. Library skills cover gRPC, GraphQL, Swagger, cobra, viper, testify, wire, dig, fx and the samber libraries. Skills cross-reference each other, so the author recommends installing the general set as a whole.

Who it is for. For Go developers who want idiomatic agent-written code in production projects.

Example request

Write a benchmark for the parser, capture a pprof profile and compare results before and after optimizing

Limitations

The full set uses a lot of context when several skills trigger. Some skills expect go, golangci-lint or benchstat installed. Some guidance reflects the author's preferences and may differ from team rules, although several skills are overridable.

How to disable. Uninstall the plugin via /plugin in Claude Code, the extension via gemini extensions uninstall, or delete the cc-skills-golang folder from the skills directory.

Security check

• Skills allow the agent to run go, golangci-lint and git in the project
• Some skills fetch documentation from the web

README in short

The README stresses that the skills began as distilled commits but were reviewed and rewritten by a human. It gives install paths via skills CLI, a Claude Code plugin, a Gemini CLI extension and copying for Cursor, Copilot, OpenCode, Codex and Antigravity. Skills are grouped into code quality, architecture, QA and performance, project start and libraries, each with its token weight. An evaluation summary compares runs with and without skills. MIT licensed.

SKILL.md

---
name: golang-benchmark
description: "Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skills-golang@golang-performance` provides the optimization patterns."
user-invocable: true
license: MIT
compatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.
metadata:
  author: samber
  version: "1.3.2"
  openclaw:
    homepage: https://github.com/samber/cc-skills-golang
    requires:
      bins:
        - go
        - benchstat
    install:
      - kind: go
        package: golang.org/x/perf/cmd/benchstat@latest
        bins: [benchstat]
allowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch Bash(benchstat:*) Bash(benchdiff:*) Bash(cob:*) Bash(gobenchdata:*) Bash(curl:*) mcp__context7__resolve-library-id mcp__context7__query-docs WebSearch AskUserQuestion EnterWorktree ExitWorktree
paths:
  - "**/*.go"
---

**Persona:** You are a Go performance measurement engineer. You never draw conclusions from a single benchmark run — statistical rigor and controlled conditions are prerequisites before any optimization decision.

**Dependencies:**

- benchstat: `go install golang.org/x/perf/cmd/benchstat@latest`

# Go Benchmarking & Performance Measurement

Performance improvement does not exist without measures — if you can measure it, you can improve it.

Related