diagnose

Guide users through reproduce-minimize-hypothesize-instrument-fix-regression-test workflows for debugging failures.

Updated May 26, 2026
One-click install
npx skills add https://github.com/anukkrit149/anukkrit-skills --skill diagnose-anukkrit149
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/anukkrit149/anukkrit-skills/tree/main/cloud/skills/diagnose
Command: npx skills add https://github.com/anukkrit149/anukkrit-skills --skill diagnose-anukkrit149

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you systematically diagnose hard bugs and performance regressions so you can reliably find the root cause instead of guessing or thrashing through code.

Core Features & Use Cases

  • Build a tight feedback loop that turns the bug into a fast, deterministic pass/fail signal for bisection, hypothesis testing, and instrumentation.
  • Reproduce and validate the exact failure so the investigation targets the same symptom the user reports.
  • Generate falsifiable hypotheses and instrument deliberately using one-variable-at-a-time probes, then verify the fix with regression testing and cleanup.

Use case example: A service is throwing intermittent errors and latency has grown after a recent change; use this skill to construct a reproducible harness, rank hypotheses, instrument the system with tagged probes, implement the fix, and lock it in with a regression test.

Quick Start

Tell the AI: "diagnose this bug: it started after the last deploy, I see this error message and it happens in this scenario; first help me build a reproducible feedback loop and then guide me through hypotheses, instrumentation, and a regression test."

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 I can't easily reproduce?

Debugging a hard bug starts by reproducing the exact failure to create a deterministic pass/fail signal. This enables systematic codebase exploration, falsifiable hypothesis ranking, and bisection to isolate the root cause instead of guessing.

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

Finding the root cause of a performance regression requires mapping one-variable-at-a-time probes to your ranked hypotheses. You instrument the system with tagged probes to measure latency changes, verify the fix, and lock it in with regression testing.

How do I use git bisect to narrow down a codebase regression?

Git bisect narrows down a codebase regression by using a reproducible test harness to generate an actionable pass/fail signal. This deterministic signal allows bisection to systematically identify the exact commit that introduced the incorrect output or thrown error.

How do I systematically debug intermittent errors in my service?

Systematically debugging intermittent errors involves constructing a reproducible feedback loop that captures the exact symptom. You then generate falsifiable hypotheses, instrument with deliberate probes, and verify the fix by rerunning the original scenario and cleaning up instrumentation.

Can I use this disciplined debugging workflow for latency slowdowns and thrown errors?

Yes, the disciplined debugging workflow applies to latency slowdowns, thrown errors, and incorrect outputs. It guides you through reproduce-minimize-hypothesize-instrument-fix-regression-test phases to reliably find the root cause across various failure types.