skills.rest
vessux
vessuxCOMMUNITY
Explore all skills by this author →
GitHub

diagnose

Reproduce, hypothesise, instrument, fix, and regression-test hard bugs.

1|Updated May 20, 2025
Search Tags:#debug#instrumentation#diagnose#hypothesis#regression-testing#bug-reproduction
One-click install
npx skills add https://github.com/vessux/dotfiles --skill diagnose-vessux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/vessux/dotfiles/tree/main/umbel/skills/pocock/diagnose
Command: npx skills add https://github.com/vessux/dotfiles --skill diagnose-vessux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This discipline provides a repeatable, end-to-end process for diagnosing hard bugs and performance regressions, reducing time to fix by enforcing a structured workflow.

Core Features & Use Cases

  • Establishes a repeatable feedback loop: reproduce → minimise → hypothesise → instrument → fix → regression-test.
  • Applies across codebases and teams, guiding developers and SREs through a rigorous debugging routine.
  • Useful for incidents, flaky bugs, performance regressions, and complex integration issues.

Quick Start

Initiate Phase 1, reproduce the failure, and follow the steps to hypothesise, instrument, fix, and 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 and reproduce hard bugs and performance regressions?▼

Debugging hard bugs and performance regressions requires a disciplined diagnostic loop that guides you through reproduce, minimise, hypothesise, instrument, fix, and regression-test phases to ensure safe, testable workflows.

What is the best way to structure a bug diagnosis workflow for complex integration issues?▼

A structured bug diagnosis workflow enforces explicit phase criteria and deterministic signals across an end-to-end diagnostic loop, reducing time to fix for complex integration issues and incidents.

How do I create a hypothesis and instrument code to fix flaky bugs?▼

To fix flaky bugs, create a hypothesis and instrument code within a repeatable feedback loop enforcing deterministic signals, guiding developers safely from bug reproduction to a validated fix.

Can I use a structured diagnostic loop for regression-testing across different codebases?▼

Yes, this structured diagnostic loop applies universally across different codebases for regression-testing, guiding developers and SREs through rigorous, safe debugging routines in real-world scenarios.

When should I not use a disciplined debugging routine for bug reproduction?▼

Avoid a disciplined debugging routine for bug reproduction when an issue is trivial, lacks deterministic signals, or cannot be safely minimized and instrumented within a testable workflow.

Related Skills

Explore More Software Engineering Skills→
santosomarsantosomar
1

test-case-reducer

Reduce large failing test inputs to minimal forms using delta debugging.

Community
Intermediate
cloudofgeorgecloudofgeorge

diagnose

Reproduce, instrument, and fix bugs with regression testing.

Community
Intermediate
helderbertohelderberto
12

diagnose

Guide a six-phase debugging loop from reproduction to regression testing.

Community
Advanced
openshift-engopenshift-eng
112

Logs Analysis

Analyze sosreport logs to identify root causes of system failures.

Community
Intermediate