skills.rest
louderthanthunderx1
louderthanthunderx1COMMUNITY
Explore all skills by this author →
GitHub

diagnose

Diagnose hard bugs and performance regressions through a structured six-phase workflow.

Updated May 21, 2026
Search Tags:#performance#debug#instrumentation#diagnose#root-cause#reproducible#bug
One-click install
npx skills add https://github.com/louderthanthunderx1/loki-skills --skill diagnose-louderthanthunderx1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/louderthanthunderx1/loki-skills/tree/main/skills/engineering/diagnose
Command: npx skills add https://github.com/louderthanthunderx1/loki-skills --skill diagnose-louderthanthunderx1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce, minimise, hypothesise, instrument, fix, and regression-test in a repeatable process.

Core Features & Use Cases

  • Structured six-phase workflow guiding reproducibility, hypothesis testing, instrumentation, fixes, and verification.
  • Helps engineers triage failures, flaky tests, and performance regressions with guardrails and repeatable evidence.
  • Use case: when a user reports a bug or slowdown, follow Phase 1 to build a reliable reproduction and a plan for fixing.

Quick Start

Build a deterministic reproduction loop for the reported bug and start Phase 1.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug a hard bug that is difficult to reproduce?▼

Debug a hard bug by building a deterministic reproduction loop, then follow a structured workflow to minimize the case, test explicit hypotheses, and apply safe instrumentation to isolate the root cause.

What is the best way to diagnose a performance regression in my code?▼

To diagnose a performance regression, apply a disciplined phase-based workflow that establishes reproducibility, forms hypotheses, adds instrumentation to measure slowdowns, and verifies the fix with regression tests.

How do I systematically find the root-cause of a flaky test?▼

Find the root-cause of a flaky test by executing a repeatable diagnosis loop that triages the failure, establishes a reliable reproduction, tests defined hypotheses, and instruments the code for deterministic evidence.

Can I use a structured debugging workflow for any codebase?▼

Yes, this structured debugging workflow applies across codebases when users report defects or describe slowdowns, guiding reproducibility, hypotheses, instrumentation, and fixes to ensure deterministic and testable outcomes.

Why should I use explicit hypotheses when diagnosing a bug?▼

Explicit hypotheses prevent blind changes during bug diagnosis by forcing you to define expected outcomes before instrumenting, ensuring you gather repeatable evidence and apply fixes that produce deterministic, testable results.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
assofohdzassofohdz
25

diagnose

Diagnose intermittent software bugs and performance regressions through a disciplined debugging workflow.

Community
Advanced
SriRamkunamsettySriRamkunamsetty

systematic-debugging

Guide software teams through four debugging phases to identify root causes.

Community
Advanced
Minara-AIMinara-AI
28

diagnose

Diagnose software defects through a structured six-phase debugging loop.

Official
Advanced