One-click install
npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill diagnose-johanneskonings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/JohannesKonings/JohannesKonings.github.io/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill diagnose-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates unproductive, ad-hoc debugging sessions for complex hard bugs and performance regressions that waste developer time and often lead to incomplete, temporary fixes.

Core Features & Use Cases

  • Structured 6-phase diagnostic loop: Enforces a repeatable process of building a feedback loop, reproducing the bug, generating falsifiable hypotheses, instrumenting code, implementing fixes with regression tests, and post-mortem cleanup.
  • Feedback loop prioritization: Guides users to build fast, deterministic reproduction loops first, cutting debugging time drastically even for non-deterministic flaky bugs.
  • Use case: If a recent deploy caused a 30% spike in page load time, or users are reporting intermittent 500 errors that can't be easily reproduced, use this skill to follow a proven process to identify the root cause and implement a permanent fix with regression testing.

Quick Start

Use the diagnose skill to investigate the intermittent checkout failures reported by users after the latest payment gateway update.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug intermittent software bugs that are hard to reproduce?

Debugging intermittent software bugs requires building a deterministic feedback loop first to reliably reproduce the failure, then generating falsifiable hypotheses to systematically test and isolate the root cause. This structured diagnostic workflow eliminates inefficient unstructured debugging sessions.

What is the best way to find the root cause of a performance regression after deployment?

Finding the root cause of a performance regression involves a 6-phase diagnostic workflow: reproducing the regression, instrumenting the code, testing falsifiable hypotheses, and implementing fixes with mandatory regression testing. This ensures permanent root cause resolution rather than temporary patches.

How do you structure a diagnostic workflow for complex functional defects?

A structured diagnostic workflow for complex functional defects follows six phases: building a feedback loop, reproducing the bug, generating falsifiable hypotheses, instrumenting code, implementing fixes with regression tests, and performing post-mortem cleanup to ensure permanent resolution.

Does structured root cause analysis work for flaky test failures?

Structured root cause analysis works for flaky test failures by prioritizing the construction of fast, deterministic feedback loops. This allows you to reproduce non-deterministic errors reliably and apply falsifiable hypothesis testing to isolate the underlying defect.

Why do my software bug fixes keep regressing after deployment?

Software bug fixes regress after deployment when they lack mandatory regression testing. A structured diagnostic workflow enforces writing regression tests alongside the fix and performing post-mortem cleanup to ensure the root cause is permanently resolved and monitored.