skills.rest
thoreinstein
thoreinsteinCOMMUNITY
Explore all skills by this author →
GitHub

bugfix

Diagnose software bugs and propose evidence-based fixes across database, service, API, and UI layers.

3|Updated Dec 25, 2025
Search Tags:#architecture#debugging#documentation#instrumentation#bugfix#root-cause-analysis#incident-response
One-click install
npx skills add https://github.com/thoreinstein/agents --skill bugfix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/thoreinstein/agents/tree/main/skills/bugfix
Command: npx skills add https://github.com/thoreinstein/agents --skill bugfix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering teams systematically diagnose and fix bugs by combining instrumentation, hypothesis-driven reasoning, and architecture awareness to minimize guesswork and ensure verifiable resolutions.

Core Features & Use Cases

  • Instrumentation-first diagnostics: add targeted logs, error boundaries, and performance metrics before attempting fixes.
  • Hypothesis generation & distillation: create multiple theories, then narrow to the most likely causes with evidence.
  • Architecture-aware analysis: read architecture docs to contextualize failures across layers (db, service, API, UI).
  • Structured resolution: document root cause, fix plan, tests, and prevention steps; use templates for consistency.
  • Collaboration gatekeeping: require explicit user confirmation before implementing fixes.

Quick Start

Begin by collecting bug context and architecture information, then enable instrumentation, reproduce the bug, generate hypotheses, present the diagnosis, and await confirmation before coding a fix.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I debug production incidents across database, service, API, and UI layers?▼

Debug production incidents by collecting architecture context, enabling targeted instrumentation, and generating evidence-based hypotheses to isolate root causes across database, service, API, and UI layers.

What's the best way to find a root cause when reproducing a complex software defect?▼

Find root causes by combining instrumentation-first diagnostics with hypothesis generation, narrowing multiple theories down to the most likely cause using collected evidence before attempting fixes.

How do I add instrumentation to diagnose bugs without guessing at the fix?▼

Add targeted logs, error boundaries, and performance metrics before attempting fixes to gather evidence, ensuring verifiable resolutions instead of relying on guesswork for complex defects.

Can I use hypothesis-driven reasoning to fix bugs in distributed system architectures?▼

Yes, hypothesis-driven reasoning contextualizes failures by reading architecture docs to analyze defects across database, service, API, and UI layers, ensuring safe and documented resolutions.

How do I document a bug resolution with root cause, fix plan, and prevention steps?▼

Document bug resolutions using structured templates that capture the root cause, fix plan, tests, and prevention steps, requiring explicit user confirmation before implementing the actual code fix.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
AndyAnh174AndyAnh174

debugger

Identify root causes of errors and test failures from messages and stack traces.

Community
Advanced
koralliskorallis
90

monitoring-observability

Implement monitoring, logging, metrics, and tracing with Grafana and Sentry.

Community
Intermediate
hariprasath-dlhhariprasath-dlh

rootmind

Automate incident response with anomaly detection, root cause analysis, and code fixes.

Community
Advanced