golang-troubleshooting

Troubleshoot Go programs using Delve and structured debugging methodology.

23|1|Updated May 10, 2026
One-click install
npx skills add https://github.com/berksunduri/GOPost --skill golang-troubleshooting-berksunduri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-troubleshooting
Source: https://github.com/berksunduri/GOPost/tree/main/.agents/skills/golang-troubleshooting
Command: npx skills add https://github.com/berksunduri/GOPost --skill golang-troubleshooting-berksunduri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dlv, go, golangci-lint, git, godebug, pprof, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps troubleshoot and debug Go programs systematically, identifying and fixing the root cause of bugs, crashes, deadlocks, or unexpected behavior.

Core Features & Use Cases

  • Debugging Methodology: Follows a structured methodology for debugging Go programs, including decision trees, Golden Rules, and a step-by-step guide.
  • Common Go Pitfalls: Identifies common Go bugs like nil pointer dereference, interface nil gotcha, variable shadowing, slice/map/defer/error/context pitfalls, race conditions, and silent error swallowing.
  • Diagnostic Tools: Utilizes diagnostic tools such as Delve, GODEBUG tracing, race detection, and pprof for performance analysis.
  • Use Case: When encountering a bug in a Go program, this Skill can help trace the issue back to its root cause, provide debugging tips, and suggest potential fixes.

Quick Start

Run the golang-troubleshooting skill to debug a specific issue in your Go code.

Frequently Asked Questions about golang-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically debug a nil pointer dereference or unexpected crash in my Go program?

Systematic Go debugging identifies crash root causes by tracing nil pointer dereferences and common pitfalls using a structured decision tree and Delve diagnostic tool. It applies a step-by-step methodology to trace unexpected behavior back to its origin.

What is the best way to find race conditions and deadlocks in Golang?

Finding race conditions and deadlocks in Golang requires utilizing race detection tools and GODEBUG tracing for concurrency analysis. A structured debugging methodology pinpoints synchronization failures and silent error swallowing causing the deadlock.

Do I need Delve and pprof installed to troubleshoot my Go code?

Yes, you need Delve and pprof installed to troubleshoot Go code effectively. These diagnostic tools are required dependencies for performance analysis, race detection, and executing the structured step-by-step debugging guide.

How do I debug variable shadowing and interface nil gotchas in Go?

Debugging variable shadowing and interface nil gotchas in Go involves identifying common language pitfalls through a structured debugging methodology. It traces silent errors and slice or map misuse to locate the exact root cause.

When should I use pprof versus GODEBUG tracing for Go performance analysis?

Use pprof for Go performance analysis when profiling CPU and memory bottlenecks, while GODEBUG tracing helps track runtime execution and garbage collection details. A structured methodology combines both to isolate root causes effectively.