openagent-systematic-debugging

Identify and resolve bugs through OpenAgent's four-phase approval-gated debugging workflow.

Updated Sep 16, 2025

Search Tags:#debugging #investigation #reporting #phases #root-cause #approval-gates #openagent

Ready to run

npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-systematic-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openagent-systematic-debugging
Source: https://github.com/SvenMarcus/.dotfiles/tree/main/opencode/.config/opencode/skills/custom/openagent-systematic-debugging
Command: npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-systematic-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OpenAgent systematic debugging skill provides a structured, approval-gated workflow to identify root causes before proposing fixes, reducing wasted time and rework in debugging sessions.

Core Features & Use Cases

Four-phase debugging with mandatory OpenAgent approvals at each checkpoint.
Comprehensive evidence collection and reporting to the user after each phase.
Safe, iterative hypothesis testing and implementation with clear rollback and re-analysis options.

Quick Start

Initiate a four-phase OpenAgent systematic debugging session for a failing issue, requesting phase approvals before each step and reporting findings at each checkpoint.

Frequently Asked Questions about openagent-systematic-debugging

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

FAQPage Schema

What is a systematic debugging workflow with approval gates?▼

A systematic debugging workflow with approval gates is a structured process requiring explicit user confirmation at each checkpoint before advancing through phases of root cause investigation, hypothesis testing, and safe implementation.

How do I find a root cause before applying a code fix to a failing test?▼

To find a root cause before applying a code fix, follow a four-phase debugging workflow that guides evidence collection, pattern analysis, and hypothesis testing with mandatory checkpoint approvals and evidentiary reporting.

Can I use this structured debugging process for unexpected production issues?▼

Yes, you can use this structured debugging process for unexpected production issues, failing tests, and any unpredictable behavior by initiating a four-phase investigation with mandatory approval gates before each step.

What's the best way to debug software issues without causing unnecessary rework?▼

The best way to debug software issues without rework is to use an approval-gated workflow that enforces root cause identification, iterative hypothesis testing, and comprehensive evidence reporting before implementing fixes.

How does hypothesis testing work during a root cause investigation?▼

Hypothesis testing during a root cause investigation works by iteratively validating assumptions through evidence collection and pattern analysis, with rollback and re-analysis options available at each checkpoint before proceeding to implementation.

When should I not use a four-phase debugging workflow with mandatory approvals?▼

You should not use a four-phase debugging workflow with mandatory approvals for urgent fixes requiring immediate deployment, as the explicit checkpoint verification and evidentiary reporting process intentionally slows down implementation.