golang-troubleshooting

Diagnose and fix bugs and performance issues in Go programs.

Updated May 4, 2026
One-click install
npx skills add https://github.com/VIethoangnguyenle/nexus-enterprise --skill golang-troubleshooting-viethoangnguyenle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-troubleshooting
Source: https://github.com/VIethoangnguyenle/nexus-enterprise/tree/main/.agent/skills/golang-troubleshooting
Command: npx skills add https://github.com/VIethoangnguyenle/nexus-enterprise --skill golang-troubleshooting-viethoangnguyenle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers systematically troubleshoot and fix bugs, crashes, and performance issues in Go codebases.

Core Features & Use Cases

  • Root Cause Analysis: Guides users through evidence-based debugging steps like reproducing errors and tracing data flow.
  • Debugging Methodology: Provides comprehensive procedures for diagnosing panics, race conditions, memory leaks, and performance bottlenecks.
  • Use Case: A developer encounters intermittent goroutine leaks; this Skill directs structured investigation using pprof, logs, and code review to identify root causes.

Quick Start

Describe issues to the AI clearly, then follow its instructions to reproduce, analyze, and resolve Go code problems efficiently.

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 memory leak in a Go program?

To debug a Go memory leak, this Skill guides you through reproducing the error and tracing data flow using pprof, logs, and code review to identify the root cause. It provides structured procedures for diagnosing memory issues.

What's the best way to diagnose intermittent goroutine leaks in Go?

Diagnosing intermittent goroutine leaks requires structured investigation. This Skill directs you to use pprof and analyze logs to trace data flow, helping you systematically reproduce the error and pinpoint the root cause.

How do I trace the root cause of a panic in my Go application?

Tracing the root cause of a Go panic involves evidence-based debugging steps. This Skill guides you through reproducing the error and tracing data flow to systematically diagnose and fix the crash in your codebase.

Can I use this methodology to fix race conditions and performance bottlenecks?

Yes, you can use this methodology to fix race conditions and performance bottlenecks. The Skill provides comprehensive procedures for diagnosing these specific issues using proven diagnostic tools and evidence-based debugging.

Do I need to install external dependencies to perform race detection and profiling?

No external dependencies are required to perform race detection and profiling. The Skill uses standard diagnostic tools like pprof and built-in Go profiling features to guide your debugging workflow.

Why does my Go program crash intermittently and how do I reproduce it?

Intermittent Go crashes require evidence-based debugging to reproduce. This Skill helps you systematically reproduce errors, analyze logs, and trace data flow to identify the underlying root cause of the instability.