skills.rest
daudaudinang
daudaudinangCOMMUNITY
Explore all skills by this author →
GitHub

debug-investigator

Perform read-only root-cause analysis on system errors with hypothesis testing.

Updated Apr 14, 2026
Search Tags:#debugging#investigation#reporting#hypothesis#root-cause#read-only#system-errors
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill debug-investigator-daudaudinang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-investigator
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/debug-investigator
Command: npx skills add https://github.com/daudaudinang/vibecode --skill debug-investigator-daudaudinang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers perform root-cause analysis on system errors without modifying code, enabling safer and faster fault isolation.

Core Features & Use Cases

  • Read-Only Investigation: Agents do not perform write actions without explicit approval.
  • Hypothesis-Driven Investigation: Form and test hypotheses through structured code analysis and data traces.
  • Investigation Log: Maintains a full audit trail of findings and decisions.
  • Output: Produces a root-cause report with evidence and recommended follow-ups.

Quick Start

Enter the error description and context to begin a non-destructive root-cause investigation that returns a structured report.

Frequently Asked Questions about debug-investigator

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

FAQPage Schema
What is read-only root-cause analysis and when do I need it for system errors?▼

Perform root-cause analysis by entering the error description and context. The investigation isolates faults through structured code analysis and data traces, forms testable hypotheses, and outputs a report with evidence and recommended follow-ups.

Can I use this investigation method for both frontend and backend integration issues?▼

Yes, this root-cause analysis applies to frontend, backend, and integration issues across development and production environments. It guides fault isolation, reproduction planning, and hypothesis testing without touching code.

How do I structure an investigation log for evidence-based reporting?▼

Structure an investigation log by maintaining a full audit trail of findings and decisions. The root-cause analysis workflow captures evidence-based reporting through hypothesis-driven investigations, ensuring every step from data gathering to verification is documented.

What are the limitations of non-destructive debugging in production environments?▼

Non-destructive debugging limitations require explicit approval for write actions. The read-only approach prevents code changes during fault isolation, meaning you must gather data traces and test hypotheses without directly modifying the production environment.

Related Skills

Explore More Software Engineering Skills→
knowz-ioknowz-io
1

knowzcode-telemetry

Correlate Sentry and App Insights telemetry to diagnose production errors.

Official
Intermediate
reomgitreomgit

gstack-openclaw-investigate

Guide systematic debugging and root cause analysis for code or system errors.

Community
Intermediate
incidentfoxincidentfox
654

observability

Correlate logs, metrics, and traces across multiple backends to identify root causes.

Official
Intermediate
anishs1207anishs1207
1

canary

Monitor live URLs with the browse daemon and visual baselines to detect post-deploy failures.

Community
Advanced