skills.rest
mmartinsoliv
mmartinsolivCOMMUNITY
Explore all skills by this author β†’
Website𝕏@mmartinsolivGitHub

diagnose

Diagnose hard bugs and performance regressions through reproducible feedback loops.

Updated May 8, 2026
Search Tags:#performance#debugging#instrumentation#diagnosis#regression testing#reproducibility
One-click install
npx skills add https://github.com/mmartinsoliv/dotfiles --skill diagnose-mmartinsoliv
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/mmartinsoliv/dotfiles/tree/main/agents/skills/diagnose
Command: npx skills add https://github.com/mmartinsoliv/dotfiles --skill diagnose-mmartinsoliv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you isolate and fix hard bugs, flaky failures, and performance regressions by turning vague symptoms into a disciplined debugging process.

Core Features & Use Cases

  • Reproducible Feedback Loops: Build a fast, deterministic way to confirm the issue before changing anything.
  • Root Cause Isolation: Form ranked hypotheses, instrument the right boundaries, and test one variable at a time.
  • Regression Protection: Convert the minimized repro into a regression test and verify the fix against the original scenario.
  • Use Case: Use it when a test started failing, a feature behaves inconsistently, or an app suddenly got slower and you need a structured path to the cause.

Quick Start

Ask me to diagnose the failing behavior by reproducing it, narrowing the cause, and proposing the best regression test seam.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug flaky tests and isolate nondeterministic failures?β–Ό

To debug flaky tests, establish a reproducible feedback loop, form ranked hypotheses, and instrument boundaries to test one variable at a time. Converting the minimized reproduction into a regression test confirms the fix and prevents future nondeterminism.

What is the best way to diagnose performance regressions across a codebase?β–Ό

Diagnosing performance regressions requires a structured approach: build a deterministic reproduction, rank potential causes, apply targeted instrumentation to slow paths, and verify the fix using regression testing against the original slow scenario.

How do you find the root cause of a failing test in a complex repository?β–Ό

Finding the root cause of a failing test involves narrowing down symptoms through ranked hypotheses and targeted instrumentation. Test one variable at a time within a reproducible loop to isolate the exact boundary causing the failure.

When do I need to use regression testing for debugging?β–Ό

Regression testing is needed after isolating a hard bug to confirm your fix works. Convert the minimized reproduction into a regression test, verifying the original behavior is restored and preventing the issue from reoccurring.

Does diagnosing broken CLI behavior require a reproducible feedback loop?β–Ό

Yes, diagnosing broken CLI behavior requires a reproducible feedback loop to confirm the issue before changing code. This deterministic baseline allows you to test ranked hypotheses accurately and validate the fix against the original failure.

Related Skills

Explore More Software Engineering Skills→
FabienDehopreFabienDehopre

diagnosing-bugs

Diagnose software bugs and performance regressions through structured reproduction workflows.

Community
Advanced
KanakMalpaniKanakMalpani

ai-regression-testing

Automate regression tests to detect AI-induced bugs in codebases.

Community
Advanced
jankneumannjankneumann

performance-optimization

Optimizes Core Web Vitals and latency through measure-identify-fix-verify-guard workflow with EXPLAIN ANALYZE and Lighthouse-CI.

Community
Advanced
drunkcodingdrunkcoding
4

sglang-bisect-ci-regression

Bisect SGLang CI failures to identify regression-causing PRs or environment changes.

Community
Advanced