skills.rest
shllg
shllgCOMMUNITY
Explore all skills by this author →
Website𝕏@shllg_devGitHub

diagnose

Diagnose and fix software bugs through reproduction and falsifiable hypotheses.

Updated Mar 22, 2026
Search Tags:#debugging#hypothesis testing#instrumentation#bug diagnosis#performance regression
One-click install
npx skills add https://github.com/shllg/night-orch --skill diagnose-shllg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/shllg/night-orch/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/shllg/night-orch --skill diagnose-shllg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a disciplined diagnosis loop for hard bugs and performance regressions, guiding you through the process of reproducing, hypothesizing, and fixing issues efficiently.

Core Features & Use Cases

  • Structured Bug Diagnosis: Follows a disciplined loop to diagnose and fix bugs.
  • Reproduction Loop: Automates the reproduction of bugs for easier debugging.
  • Hypothesis Testing: Encourages the creation of falsifiable hypotheses to narrow down the problem.
  • Instrumentation: Utilizes targeted logging and debugging tools to isolate issues.
  • Regression Testing: Ensures that fixes do not introduce new bugs.
  • Use Case: When a user reports a bug or performance regression, this Skill can help you systematically identify and resolve the issue.

Quick Start

Use the diagnose skill to systematically address a reported bug in your codebase.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically diagnose a hard bug in my software application?▼

Structured bug diagnosis requires a disciplined loop to reproduce the issue, formulate falsifiable hypotheses, and use targeted debugging tools to isolate and fix the root cause efficiently.

What is the best way to narrow down a performance regression in my codebase?▼

Performance regression diagnosis works best when you automate the reproduction loop, create falsifiable hypotheses to narrow down the problem, and apply targeted instrumentation to isolate the issue.

How does hypothesis testing work when debugging software?▼

Hypothesis testing in debugging involves creating falsifiable hypotheses to systematically narrow down the problem, verifying specific assumptions rather than guessing the root cause blindly.

Do I need to understand my codebase before using a structured debugging approach?▼

Yes, a structured debugging approach requires a clear understanding of the codebase and debugging techniques to effectively reproduce issues, instrument targeted logging, and isolate the root cause.

Why should I automate the reproduction loop when fixing bugs?▼

Automating the reproduction loop ensures consistent bug recreation for easier debugging, allowing you to reliably test falsifiable hypotheses and verify that fixes do not introduce new regressions.

What instrumentation is needed to isolate a bug during diagnosis?▼

Instrumentation for bug diagnosis utilizes targeted logging and specific debugging tools to isolate issues, providing the necessary telemetry to confirm or deny your falsifiable hypotheses accurately.

Related Skills

Explore More Software Engineering Skills→
royhenengelroyhenengel

debug

Guide systematic debugging workflows for identifying and resolving software defects.

Community
Intermediate
hachejhachej
45

diagnosing-bugs

Guide six-phase debugging to reproduce, isolate, and verify software bug fixes.

Community
Advanced
giljaegiljae
1

gstack-canary

Monitor live web apps for console errors, performance, and visual regressions post-deploy.

Community
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic