skills.rest
Jmarques
JmarquesCOMMUNITY
Explore all skills by this author →
GitHub

diagnosing-bugs

Guide structured debugging with feedback loops and hypothesis testing.

Updated Jul 3, 2026
Search Tags:#code analysis#debugging#software development#bug diagnosis#performance regression
One-click install
npx skills add https://github.com/Jmarques/orford-sur-le-lac_embarcations --skill diagnosing-bugs-jmarques
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/Jmarques/orford-sur-le-lac_embarcations/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/Jmarques/orford-sur-le-lac_embarcations --skill diagnosing-bugs-jmarques

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of diagnosing hard-to-find bugs and performance regressions, guiding users through a systematic approach to debugging.

Core Features & Use Cases

  • Feedback Loop Construction: Develop a tight feedback loop to quickly identify the source of a bug or performance issue.
  • Reproduction and Minimization: Reproduce the bug in a minimal scenario and shrink it to the smallest possible reproduction case.
  • Hypothesis Generation: Formulate and test hypotheses about the root cause of the bug.
  • Instrumentation: Use targeted logging and debugging techniques to gather information about the bug.
  • Regression Testing: Ensure the bug is fixed and that the fix does not introduce new issues.

Quick Start

To begin diagnosing a bug, run the feedback loop with the provided command and follow the steps outlined in the Skill's guide.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
What is the best way to diagnose hard-to-find bugs and performance regressions?▼

To debug hard-to-find bugs, construct a tight feedback loop, reproduce the bug in a minimal scenario, generate root cause hypotheses, and use targeted instrumentation to systematically test your assumptions.

How do I reproduce a bug in a minimal scenario to find the root cause?▼

To reproduce a bug in a minimal scenario, shrink the issue to the smallest possible reproduction case, apply targeted logging for instrumentation, and formulate hypotheses to systematically test and isolate the root cause.

How do I set up a tight feedback loop for software debugging?▼

A tight feedback loop for software debugging requires a deep understanding of the codebase, allowing you to iterate quickly between bug reproduction, targeted logging, and systematic hypothesis testing to pinpoint the issue.

Do I need a deep understanding of my codebase to perform systematic bug diagnosis?▼

Yes, systematic bug diagnosis requires a deep understanding of the codebase and debugging techniques to effectively guide the process of feedback loop construction, hypothesis generation, and targeted instrumentation.

How do I ensure a bug fix does not introduce new performance regressions?▼

To ensure a bug fix does not introduce new performance regressions, implement regression testing after resolving the issue, verifying that the original bug is fixed without causing new problems in the software application.

Related Skills

Explore More Software Engineering Skills→
stellastella
163

regression-hunt

Identify regression root causes and propose minimal regression tests.

Official
Intermediate
QunnnnQunnnn

dart-add-unit-test

Create unit tests for Dart functions, methods, and classes using package:test.

Community
Intermediate
kssuminkssumin

perf-tuning-cycle

Orchestrate performance tuning loops with k6, Prometheus, and Grafana reports.

Community
Advanced
BradliebsBradliebs

canary

Monitor live web apps for console errors, performance regressions, and visual anomalies.

Community
Advanced