go-test-debug

Diagnose Go test failures including panics, timeouts, races, and flakes across packages and subtests.

2|1|Updated Apr 10, 2023
One-click install
npx skills add https://github.com/popoffvg/dotfiles --skill go-test-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-test-debug
Source: https://github.com/popoffvg/dotfiles/tree/main/skills/go-test-debug
Command: npx skills add https://github.com/popoffvg/dotfiles --skill go-test-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and diagnose Go test failures using an error-first, evidence-driven workflow to minimize debugging time.

Core Features & Use Cases

  • Systematic failure classification (build errors, assertion failures, panics, race conditions, timeouts, flaky tests)
  • Layered diagnosis steps: collect failure output, classify, perform targeted checks, and propose fixes
  • Repro and validate: isolate failing tests, re-run with focused scopes, and validate fixes with repeatable runs

Quick Start

Run the failing Go test, capture the output, and I will guide you through diagnosing and fixing it using the described workflow.

Frequently Asked Questions about go-test-debug

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

FAQPage Schema
How do I diagnose flaky Go tests and data races across packages?

Diagnose flaky Go tests by capturing failure output to classify panics, timeouts, and data races. The error-first workflow isolates failing subtests across packages and performs targeted checks to propose structured fixes.

What is the best way to debug Go test panics and timeouts systematically?

Debug Go test panics and timeouts using a layered diagnosis workflow. Collect failure output, classify the build or runtime error, perform targeted checks to isolate the root cause, and validate fixes with repeatable test runs.

How do I fix Go test failures using an evidence-driven workflow?

Fix Go test failures by applying diff-driven diagnosis to compare outputs and perform layered verification. This error-first approach ensures you collect evidence, classify the failure type, and propose structured remediation steps.

Can I re-run isolated Go subtests to validate proposed fixes?

You can isolate failing Go subtests and re-run them with focused scopes to validate fixes. This repro and validate step ensures repeatable runs confirm the structured remediation before closing the diagnosis workflow.

Does this Go test debugging approach work for build errors and assertion failures?

This approach handles systematic failure classification for build errors, assertion failures, panics, race conditions, timeouts, and flaky tests. It enforces an error-first workflow with targeted checks to diagnose failures across all packages.