skills.rest
nkabbara
nkabbaraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

diagnosing-bugs

Diagnose hard-to-find bugs and performance regressions using a phase-based feedback loop.

Updated Jan 29, 2026
Search Tags:#code analysis#debugging#feedback loop#bug diagnosis#performance regression
One-click install
npx skills add https://github.com/nkabbara/dotfiles --skill diagnosing-bugs-nkabbara
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/nkabbara/dotfiles/tree/main/exact_dot_agents/exact_skills/exact_mattpocock/exact_diagnosing-bugs
Command: npx skills add https://github.com/nkabbara/dotfiles --skill diagnosing-bugs-nkabbara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnose and debug hard-to-find bugs and performance regressions, helping you to build a tight feedback loop for efficient problem-solving.

Core Features & Use Cases

  • Feedback Loop Construction: Offers various methods to construct a tight feedback loop for identifying and validating bugs.
  • Phase-Based Approach: Follows a structured six-phase approach for debugging, including build a feedback loop, reproduce + minimize, hypothesise, instrument, fix + regression test, and cleanup + post-mortem.
  • Use Case: When you encounter a hard bug or performance regression, use this Skill to systematically diagnose and resolve the issue.

Quick Start

Run the skill with the command 'diagnose-bugs' and follow the phase-based approach to debug the issue.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I debug a hard-to-find performance regression systematically?▼

Debug a performance regression by constructing a tight feedback loop through a six-phase approach: reproduce and minimize the issue, hypothesize, instrument, fix with a regression test, and clean up. A clear pass/fail signal is required to validate each iteration.

What is a tight feedback loop for bug diagnosis and when do I need it?▼

A tight feedback loop for bug diagnosis is a rapid cycle of reproducing, hypothesizing, and validating a code issue. You need it when diagnosing hard-to-find bugs where the root cause is not immediately obvious from standard code analysis.

How do I reproduce and minimize a bug before attempting a fix?▼

Reproduce and minimize a bug by executing scripts within a structured feedback loop to isolate the exact trigger. This minimization phase reduces the variables needed to consistently recreate the pass/fail signal before hypothesizing the root cause.

Can I use code analysis scripts to diagnose bugs without a clear pass/fail signal?▼

Diagnosing bugs without a clear pass/fail signal is not supported. The structured debugging approach requires a definitive pass/fail signal to instrument the code, validate hypotheses, and confirm the fix across the feedback loop.

What's the best way to instrument code when diagnosing a complex bug?▼

The best way to instrument code for bug diagnosis is within a structured feedback loop, using scripts to execute commands that validate hypotheses. This instrumentation phase directly follows issue minimization and precedes the final fix and cleanup.

Related Skills

Explore More Software Engineering Skills→
vladpolewoivladpolewoi

diagnose

Diagnose software bugs and performance regressions through structured hypothesis testing.

Community
Advanced
adriannoesadriannoes
46

diagnose

Diagnose software bugs and performance regressions with a structured debugging workflow.

Community
Advanced
riethmayerriethmayer
2

diagnose

Diagnose hard bugs through a six-phase reproduction-to-regression-check loop.

Community
Advanced
lyingparachutelyingparachute

diagnosing-bugs

Diagnose hard bugs and performance regressions through a structured feedback loop.

Community
Advanced