golang-troubleshooting

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill) or applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill).

跳到安装

仓库: samber/cc-skills-golang
最近来源活动: 2026年7月6日 15:20
检测到的 SKILL.md 语言: 英语
星标: 2,997
分支: 196

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

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

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

12 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

golang-lint

Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive.

2026-08-13

golang-how-to

Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures CLAUDE.md or AGENTS.md to force-trigger skills in a project (/golang-how-to configure).

2026-07-27

golang-project-layout

Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.

2026-07-27

查看这个仓库的全部 Skills

Go Troubleshooting Guide

NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Symptom fixes create new bugs and waste time. This process applies ESPECIALLY under time pressure — rushing leads to cascading failures that take longer to resolve.

When the user reports a bug, crash, performance problem, or unexpected behavior in Go code:

Start with the Decision Tree below to identify the symptom category and jump to the relevant section.

Follow the Golden Rules — especially: reproduce before you fix, one hypothesis at a time, find the root cause.

Work through the General Debugging Methodology step by step. Do not skip steps.

Watch for Red Flags in your own reasoning. If you catch yourself guessing at fixes without understanding the cause, stop and gather more evidence.

Escalate tools incrementally. Start with the simplest diagnostic (fmt.Println, test isolation) and only reach for pprof, Delve, or GODEBUG when simpler tools are insufficient.

Never propose a fix you cannot explain. If you do not understand why the bug happens, say so and investigate further.

Quick Decision Tree

WHAT ARE YOU SEEING? "Build won't compile" → go build ./... 2>&1, go vet ./... → See [compilation.md](./references/compilation.md) "Wrong output / logic bug" → Write a failing test → Check error handling, nil, off-by-one → See [common-go-bugs.md](./references/common-go-bugs.md), [testing-debug.md](./references/testing-debug.md) "Random crashes / panics" → GOTRACEBACK=all ./app → go test -race ./... → See [common-go-bugs.md](./references/common-go-bugs.md), [diagnostic-tools.md](./references/diagnostic-tools.md) "Sometimes works, sometimes fails" → go test -race ./... → See [concurrency-debug.md](./references/concurrency-debug.md), [testing-debug.md](./references/testing-debug.md) "Program hangs / frozen" → curl localhost:6060/debug/pprof/goroutine?debug=2 → See [concurrency-debug.md](./references/concurrency-debug.md), [pprof.md](./references/pprof.md) "High CPU usage" → pprof CPU profiling → See [performance-debug.md](./references/performance-debug.md), [pprof.md](./references/pprof.md) "Memory growing over time" → pprof heap profiling → See [performance-debug.md](./references/performance-debug.md), [concurrency-debug.md](./references/concurrency-debug.md) "Slow / high latency / p99 spikes" → CPU + mutex + block profiles → See [performance-debug.md](./references/performance-debug.md), [diagnostic-tools.md](./references/diagnostic-tools.md) "Simple bug, easy to reproduce" → Write a test, add fmt.Println / log.Debug → See [testing-debug.md](./references/testing-debug.md)

Go Troubleshooting Guide

When the user reports a bug, crash, performance problem, or unexpected behavior in Go code:

Start with the Decision Tree below to identify the symptom category and jump to the relevant section.

Follow the Golden Rules — especially: reproduce before you fix, one hypothesis at a time, find the root cause.

Work through the General Debugging Methodology step by step. Do not skip steps.

Watch for Red Flags in your own reasoning. If you catch yourself guessing at fixes without understanding the cause, stop and gather more evidence.

Escalate tools incrementally. Start with the simplest diagnostic (fmt.Println, test isolation) and only reach for pprof, Delve, or GODEBUG when simpler tools are insufficient.

Never propose a fix you cannot explain. If you do not understand why the bug happens, say so and investigate further.

Quick Decision Tree

name	golang-troubleshooting
description	Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill) or applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill).
user-invocable	true
license	MIT
compatibility	Designed for Claude Code or similar AI coding agents, and for projects using Golang.
metadata	{"author":"samber","version":"1.2.3","openclaw":{"emoji":"🔍","homepage":"https://github.com/samber/cc-skills-golang","requires":{"bins":["go","dlv"]},"install":[{"kind":"go","package":"github.com/go-delve/delve/cmd/dlv@latest","bins":["dlv"]}]}}
allowed-tools	Read Edit Write Glob Grep Bash(go:) Bash(golangci-lint:) Bash(git:) Bash(dlv:) Agent WebFetch WebSearch AskUserQuestion

name	golang-troubleshooting
description	Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill) or applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill).
user-invocable	true
license	MIT
compatibility	Designed for Claude Code or similar AI coding agents, and for projects using Golang.
metadata	{"author":"samber","version":"1.2.3","openclaw":{"emoji":"🔍","homepage":"https://github.com/samber/cc-skills-golang","requires":{"bins":["go","dlv"]},"install":[{"kind":"go","package":"github.com/go-delve/delve/cmd/dlv@latest","bins":["dlv"]}]}}
allowed-tools	Read Edit Write Glob Grep Bash(go:) Bash(golangci-lint:) Bash(git:) Bash(dlv:) Agent WebFetch WebSearch AskUserQuestion

golang-troubleshooting

安装方式

检查来源文件

Go Troubleshooting Guide

Quick Decision Tree

Go Troubleshooting Guide

Quick Decision Tree

The Golden Rules

1. Read the Error Message First

2. Reproduce Before You Fix

3. If You Don't Measure It, You're Guessing

4. One Hypothesis at a Time

5. Find the Root Cause — No Workarounds

6. Research the Codebase, Not Just the Diff

7. Start Simple

Red Flags: You're Debugging Wrong

Reference Files

Cross-References

golang-troubleshooting

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Go Troubleshooting Guide

Quick Decision Tree

Go Troubleshooting Guide

Quick Decision Tree

The Golden Rules

1. Read the Error Message First

2. Reproduce Before You Fix

3. If You Don't Measure It, You're Guessing

4. One Hypothesis at a Time

5. Find the Root Cause — No Workarounds

6. Research the Codebase, Not Just the Diff

7. Start Simple

Red Flags: You're Debugging Wrong

Reference Files

Cross-References