skills.rest
autopus-ai
autopus-aiOFFICIAL
Explore all skills by this author →
GitHub

debugging

Diagnose and fix bugs through reproduction tests and root-cause analysis.

111|73|Updated Mar 20, 2026
Search Tags:#debugging#bug fix#root cause analysis#race condition#regression testing#go test#reproduction test
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill debugging-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/debugging
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill debugging-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing bugs without a systematic process often leads to patching symptoms instead of root causes, causing regressions and recurring issues. This Skill enforces a disciplined reproduce-analyze-fix-verify workflow so every bug fix is test-backed and minimal. ## Core Features & Use Cases - Reproduction-First Testing: Write a failing test that reproduces the bug before making any code changes, then confirm it passes after the fix. - Root-Cause Analysis: Classify defects as logic errors, boundary conditions, concurrency issues, type problems, or external dependency failures, with caller and shared root-cause evidence rules. - Minimal Fix & Verification: Apply the smallest possible change, then validate with reproduction tests, full regression suites, and race detection. - Use Case: A Go service intermittently fails under load. Use this Skill to write a reproduction test, run go test -race to detect the race condition, apply a minimal fix, and verify the full test suite passes. ## Quick Start Use the debugging skill to reproduce this failing behavior with a test, find the root cause, and apply a minimal verified fix.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I systematically debug a bug in Go code?▼

Start by writing a failing test that reproduces the bug with the simplest possible case. Then classify the root cause, apply a minimal fix, and verify with go test including the -race flag for concurrency issues.

How to write a reproduction test before fixing a bug?▼

Identify the exact input and state that trigger the bug, then write a test asserting the expected behavior, which should fail initially. After applying the fix, the same test must pass, confirming the bug is resolved.

How do I detect race conditions in Go tests?▼

Run go test -race ./... to enable the race detector, which instruments memory accesses and reports concurrent unsynchronized reads and writes. Combine with verbose test output and pprof profiling for deeper analysis.

Why should I avoid patching only the symptom location of a bug?▼

Patching only where the symptom appears can leave the shared root cause intact, affecting other callers. Record caller evidence first; if the symptom location is not the true root cause, mark the patch plan as revise-target.

What are the limitations of a minimal-fix debugging approach?▼

Minimal fixes deliberately exclude refactoring and broader cleanup, so underlying design issues may remain. It is best for targeted defect resolution, not for architectural problems requiring larger redesigns.

Related Skills

Explore More Software Engineering Skills→
KingInYellowsKingInYellows

ce-debug

Diagnose bugs through a phase-based investigation from symptom to root cause.

Official
Advanced
hadpadrahulhadpadrahul

gsd-audit-fix

Automate code quality issue detection, classification, and test-verified fixes.

Community
Advanced
QwenLMQwenLM
27.5k

bugfix

Fixes GitHub issue bugs using a reproduce-first workflow with test-engineer verification.

Official
Advanced
ruiyangruiyiruiyangruiyi

node-inspect-debugger

Attach the Node.js inspector and set breakpoints to debug runtime failures.

Community
Intermediate