skills.rest
Jylhis
JylhisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

golang-troubleshooting

Diagnoses and fixes Go bugs using structured, evidence-based workflows and verification tools.

1|Updated Apr 4, 2026
Search Tags:#testing#debugging#troubleshooting#golang#profiling#diagnostics#go-tools
One-click install
npx skills add https://github.com/Jylhis/claude-marketplace --skill golang-troubleshooting-jylhis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: golang-troubleshooting
Source: https://github.com/Jylhis/claude-marketplace/tree/main/plugins/golang-dev/skills/golang-troubleshooting
Command: npx skills add https://github.com/Jylhis/claude-marketplace --skill golang-troubleshooting-jylhis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Troubleshooting Go applications with a disciplined, step-by-step approach that eliminates guesswork and accelerates root-cause analysis.

Core Features & Use Cases

  • Enforces a structured debugging workflow: read the error, reproduce, hypothesize, test one change at a time, and verify the fix.
  • Provides guidance for common Go issues (nil pointers, race conditions, panics, and production latency) with references to best-practice documentation.
  • Supports teams by embedding references and tooling guidance (pprof, race detector, and testing-debug methodology) into the workflow.

Quick Start

Describe the bug and follow the Golden Rules to reproduce, measure a single hypothesis, fix the root cause, and verify with tests.

Frequently Asked Questions about golang-troubleshooting

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

FAQPage Schema
How do I debug a nil pointer dereference in Go?▼

To debug a nil pointer dereference in Go, follow a structured workflow to reproduce the panic, trace the root cause by testing one hypothesis at a time, and verify the fix with tests.

What is the best way to troubleshoot Go race conditions?▼

The best way to troubleshoot Go race conditions is to reproduce the error, use the race detector and profiling tools to test a single hypothesis, and verify the root-cause fix.

How do I diagnose production latency in a Go server?▼

Diagnose production latency in a Go server by applying an evidence-based debugging workflow that uses pprof profiling to measure a single hypothesis and verify the root cause.

Can I use this structured debugging workflow for Go CLI and library code?▼

Yes, this structured debugging workflow applies to Go CLI and library code, enforcing root-cause tracing and one-hypothesis-at-a-time testing for compilation errors and panics.

Why does my Go application panic and how do I fix the root cause?▼

Your Go application panics due to issues like nil pointers or race conditions; fix the root cause by reading the error, reproducing it, testing one change, and verifying with tests.

Related Skills

Explore More Software Engineering Skills→
vanstinatorvanstinator

golang-troubleshooting

Troubleshoots Go program crashes, races, deadlocks and hangs using evidence-first root cause analysis.

Community
Advanced
haipham22haipham22
2

golang-troubleshooting

Diagnose Go bugs, crashes, deadlocks, and flaky tests with root-cause tracing.

Community
Advanced
Harmeet10000Harmeet10000
7

golang-troubleshooting

Diagnoses Go code issues with structured root-cause analysis and fix verification.

Community
Advanced
romiluz13romiluz13
161

root-cause-analysis

Guide root cause analysis through evidence collection and hypothesis testing.

Community
Basic