skills.rest
rpelizza
rpelizzaCOMMUNITY
Explore all skills by this author →
GitHub

pelizzai-debugging

Diagnose software defects through evidence-based hypothesis testing and reversible containment.

Updated Jun 26, 2026
Search Tags:#automation#debugging#root cause analysis#incident response#software testing#triage
One-click install
npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pelizzai-debugging
Source: https://github.com/rpelizza/PelizzAI/tree/main/.agents/skills/pelizzai-debugging
Command: npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a rigorous, structured framework for diagnosing and fixing software bugs, preventing common pitfalls like guessing, thrashing, or applying ineffective fixes.

Core Features & Use Cases

  • Triage and Classification: Automatically categorizes issues into direct causes, uncertain deterministic bugs, flaky failures, or incidents with active damage.
  • Evidence-Based Resolution: Enforces the creation of a minimal, red-capable oracle to prove the symptom before attempting any fix.
  • Safety Guardrails: Mandates reversible containment for active incidents and prevents unauthorized repository mutations through a strict branching and confirmation gate.

Quick Start

Use the pelizzai-debugging skill to investigate the reported test failure in the authentication module and propose a fix based on the observed stack trace.

Frequently Asked Questions about pelizzai-debugging

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

FAQPage Schema
What is systematic evidence-based debugging for software incidents?▼

Evidence-based debugging is a structured diagnostic workflow that classifies software defects and enforces hypothesis testing with minimal red-capable proof before attempting any fix.

How do I fix flaky test failures without guessing or thrashing?▼

To fix flaky failures, use a structured triage process that categorizes the issue, builds a minimal reproduction oracle to prove the symptom, and validates proportional code changes.

How do I triage active production incidents with ongoing damage?▼

Triage active incidents by applying reversible containment to stop the bleeding immediately, then follow evidence-based hypothesis testing before deploying any permanent resolution.

What is the best way to resolve uncertain deterministic bugs across diverse environments?▼

The best way to resolve deterministic bugs is enforcing a structured diagnostic workflow that requires creating a minimal, red-capable oracle to prove the symptom before proposing a fix.

Can I apply automated root cause analysis without unauthorized repository mutations?▼

Yes, automated root cause analysis can prevent unauthorized mutations by enforcing a strict branching strategy and confirmation gate before any reversible containment or code changes are applied.

Why do my software fixes fail to resolve the original defect?▼

Software fixes fail when they bypass evidence-based hypothesis testing; a structured framework requires proving the symptom with a minimal reproduction oracle to ensure verifiable resolution.

Related Skills

Explore More Software Engineering Skills→
AstrumonAstrumon

debugging-wizard

Diagnose Kotlin/JVM bugs, coroutine deadlocks, and runtime errors with stack traces.

Community
Advanced
benediktmsbenediktms

debugger

Reproduce, isolate, fix, and verify software defects with minimal changes.

Community
Intermediate
FrantssFrantss

diagnosing-bugs

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

Community
Advanced
jscott3201jscott3201
2

incident-response

Triage production incidents by gathering symptoms, correlating changes, and guiding mitigation.

Community
Advanced