菜单
Analyze and optimize Go program performance. Use when asked to profile Go code, find performance bottlenecks, analyze memory allocations, detect memory leaks, write benchmarks, or optimize CPU/memory usage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | go-performance |
| description | Analyze and optimize Go program performance. Use when asked to profile Go code, find performance bottlenecks, analyze memory allocations, detect memory leaks, write benchmarks, or optimize CPU/memory usage. |
go tool pprof| Profile | Test Flag | HTTP Endpoint |
|---|---|---|
| CPU | -cpuprofile | /debug/pprof/profile |
| Heap | -memprofile | /debug/pprof/heap |
| Goroutine | - | /debug/pprof/goroutine |
# Generate from benchmarks
go test -bench=. -cpuprofile cpu.prof -memprofile mem.prof
# Analyze (interactive or one-liner)
go tool pprof -top -cum cpu.prof
go tool pprof -http=:8080 cpu.prof # web UI with flame graphs
# Memory analysis
go tool pprof -alloc_space -top mem.prof # bytes allocated
go tool pprof -alloc_objects -top mem.prof # allocation count (GC pressure)
# Compare profiles (find leaks/regressions)
go tool pprof -base old.prof new.prof
# Filter results
go tool pprof -focus='mypackage.*' cpu.prof
$GOPATH-base flag to find regressions between profilesEvery time we work on some performance issue, we should:
Then, we create a second benchmark, and a new production function with the changes we want.
This way we can quickly run and compare both benchmarks.
Once we're happy with the changes, we replace the old function and old benchmark with the new ones.
Commit messages should always have the benchmark results in them.
Simplify recently-changed code without changing behavior. Use by default whenever implementing anything, and when explicitly invoked (e.g. "simplify", "clean up", "refactor").
Rust specialist for code writing, reviews, refactoring, security audits, and performance optimization. Prioritizes safety, idiomatic patterns, DRY via traits/generics, simplicity, and measurable performance. Use for any Rust project work, audits, or tuning tasks.
Carlos Becker's (@caarlos0) programming style, conventions, and review habits. Use whenever pairing with Carlos on code, reviewing his PRs/issues, contributing to his projects (GoReleaser, nFPM, env, svu, fang, dotfiles, etc.), writing Go CLIs in his style, or any time the user asks to "pair with caarlos0", "code like caarlos0", or work in a way that matches his preferences.
Generate a daily maintainer briefing for a GitHub repository. Fetches open PRs, issues, CI status, and produces a prioritized attention-allocation report. Use when user says "/maintainer-briefing" or asks for a maintainer report. Examples - "/maintainer-briefing external-secrets/external-secrets", "/maintainer-briefing", "give me a maintainer briefing".
Get documentation for any Go library using `go doc`. Use when asked about Go package documentation, API reference, function signatures, or how to use a specific Go library/package.