Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Go Troubleshooting Guide · samber | DecimalAI

codingby samber

Go Troubleshooting Guide

samber/golang-troubleshooting

Source samber/cc-skills-golang ↗License MIT

Troubleshoot Golang programs systematically - find and fix the root cause.

SkillScore87Maintained

Automatic

Coding pack

Last verified 9/9/2026

What it changes

Passed 18 of 21 test cases with the skill, and 15 of 21 without it.

Without skill70%

With skill87%

Checks it passed that the model alone missed

Advises reproducing the failure with a test before writing a code fix
Mentions using ultrathink to trigger extended thinking for deep root cause analysis
Identifies 3+ failed fix attempts as a red flag indicating an incorrect mental model

and 3 more in the full report

5 fixed15 passed either way2 still failing1 broke

Pass-rate lift: +17 pp
Tokens: +147%
Agent turns: 0%
Response time: -10%

Model gemini-3.6-flashMeasured 9/9/2026v320 of 23 cases passed with skill · 21 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/samber-golang-troubleshooting/SKILL.md https://app.decimal.ai/s/samber-golang-troubleshooting/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add samber-golang-troubleshooting, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/samber-golang-troubleshooting/ and pins it in .decimal/skills.lock

decimalai skills add samber-golang-troubleshooting

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/samber-golang-troubleshooting/SKILL.md https://app.decimal.ai/s/samber-golang-troubleshooting/SKILL.md

Raw file: /s/samber-golang-troubleshooting/SKILL.md ↗ · machine-readable summary at /s/samber-golang-troubleshooting.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 5

Prompt

A developer received `cannot use req (type *UserRequest) as type Validator in argument to ValidateUser`. Without editing code yet, what is the first rule of debugging this error?

What was checked, without and with the skill
Checked	Without skill	With skill
Instructs reading the exact error message details to check type signatures and interface satisfaction before making changes	Missed	Passed

case-18 · gemini-3.6-flash · 9/9/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md171 lines11 files

Persona: You are a Go systems debugger. You follow evidence, not intuition — instrument, reproduce, and trace root causes systematically.

Thinking mode: Reason as thoroughly as possible for debugging and root cause analysis — rushed reasoning leads to symptom fixes, deep thinking finds the actual root cause. On Claude Code, use ultrathink to trigger extended thinking explicitly.

Orchestration mode: Fan out the five bug-category sub-agents described in Codebase bug hunt mode for a codebase-wide bug hunt. A single-issue debug session should stay sequential; orchestration only pays off when scanning broadly for unknown bugs. On Claude Code, use ultracode to opt into multi-agent orchestration explicitly.

Modes:

Single-issue debug (default): Follow the sequential Golden Rules — read the error, reproduce, one hypothesis at a time. Do not launch sub-agents; focused sequential investigation is faster for a single known symptom.
Codebase bug hunt (explicit audit of a large codebase): Launch up to 5 parallel sub-agents, one per bug category (nil/interface, resources, error handling, races, context/slice/map). Use this mode when the user asks for a broad sweep, not when debugging a specific reported issue.

Dependencies:

dlv: go install github.com/go-delve/delve/cmd/dlv@latest

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)

Track record

Benchmark

18 / 21

test cases passed, vs 15 / 21 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/8/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

samber / cc-skills-golang

skills/golang-troubleshooting/SKILL.md

View on GitHub ↗

License MITImported 9/8/2026Version v3Bundled 10 files

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Go Troubleshooting Guide

Quick Decision Tree

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills