skills.rest
michael-conrad
michael-conradCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnoses bugs via root-cause analysis and hypothesis testing in a read-only workflow.

Updated Apr 24, 2026
Search Tags:#automation#debug#orchestration#diagnose#root-cause#hypothesis-testing
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill systematic-debugging-michael-conrad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/michael-conrad/.opencode --skill systematic-debugging-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix bugs via rooted-cause analysis and hypothesis testing, ensuring changes are justified and minimal.

Core Features & Use Cases

  • Enforces read-only diagnosis to prevent premature edits.
  • Routes issues to sub-agents for independent investigation and evidence-based conclusions.
  • Requires explicit authorization before applying any fixes and maintains auditability.

Quick Start

Activate the skill and begin with the diagnose task to perform read-only analysis before attempting any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is root-cause analysis and how does hypothesis testing work for software debugging?▼

Systematic debugging enforces read-only diagnosis using sub-agents for independent investigation, requiring verifiable evidence before any fixes are authorized. It reproduces and isolates issues to support evidence-based conclusions.

How do I diagnose bugs without making premature code changes?▼

Enforce read-only diagnosis by routing issues to sub-agents for independent investigation, preventing premature edits. Explicit authorization is required before applying minimal fixes to ensure traceable remediation.

What's the best way to orchestrate sub-agents for systematic bug diagnosis?▼

Orchestrate sub-agents through a defined task-prompt contract to coordinate independent investigations. This ensures traceable, auditable remediation by gathering verifiable evidence before authorizing minimal fixes.

Can I apply code fixes immediately during the bug diagnosis process?▼

No, the diagnosis process is strictly read-only and prevents premature edits. Explicit authorization is required before applying any code changes, ensuring minimal fixes are justified, traceable, and auditable.

When do I need a read-only workflow for debugging and root-cause analysis?▼

A read-only workflow is needed when issues must be reproduced, isolated, and supported by evidence before authoring fixes. It enforces minimal fixes and requires explicit authorization for traceable remediation.

Related Skills

Explore More Software Engineering Skills→
automagik-devautomagik-dev
328

trace

Reproduce software failures and isolate root causes with read-only tools.

Official
Intermediate
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
vladpolewoivladpolewoi

debrief

Automate post-incident analysis and generate debrief documents from codebase evidence.

Community
Advanced
cin12211cin12211
1

gitnexus-debugging

Trace execution paths and call graphs with GitNexus commands.

Community
Advanced