skills.rest
utsavanand
utsavanandCOMMUNITY
Explore all skills by this author →
GitHub

uvs-investigate

Automate structured root-cause debugging with a three-attempt cap and provenance-rich reports.

2|Updated Apr 11, 2026
Search Tags:#debug#reporting#provenance#investigate#root-cause#bug-triage
One-click install
npx skills add https://github.com/utsavanand/uv-suite --skill uvs-investigate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uvs-investigate
Source: https://github.com/utsavanand/uv-suite/tree/main/skills/uvs-investigate
Command: npx skills add https://github.com/utsavanand/uv-suite --skill uvs-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured root-cause debugging to trace data flow, validate hypotheses, and escalate after three failed attempts.

Core Features & Use Cases

  • Guided investigative workflow: reproduce, narrow scope, and test hypotheses to isolate root causes.
  • Structured artifact generation: reports with provenance and session context for auditability.
  • Escalation and governance: enforces a three-attempt cap and prompts escalation when unresolved.

Quick Start

Describe the failure and start a guided debugging session to begin the investigation.

Frequently Asked Questions about uvs-investigate

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

FAQPage Schema
How do I automate root-cause debugging for tricky software bugs?▼

Automated root-cause debugging traces data flow and validates hypotheses to isolate software bugs. It guides you through reproducing failures, narrowing scope, and testing hypotheses to pinpoint the underlying cause.

What is the best way to investigate flaky tests and runtime errors in a CI pipeline?▼

Investigating flaky tests and runtime errors requires a structured workflow to reproduce failures and validate hypotheses across environments. This approach isolates the root cause by systematically narrowing the scope of the failure.

How does structured bug triage generate provenance-rich reports?▼

Structured bug triage generates provenance-rich reports by tracing data flow and recording session context during hypothesis validation. These artifacts provide full auditability for tracking how the root cause was identified.

What happens when root-cause investigation fails to resolve a bug?▼

When root-cause investigation fails to resolve a bug after three attempts, the process enforces a three-attempt cap and automatically prompts escalation. This governance prevents endless debugging loops on unresolved failures.

Can I use a guided debugging workflow for runtime errors across different environments?▼

Guided debugging workflows apply to runtime errors across codebases, CI pipelines, and environments. You start by describing the failure, which initiates a structured session to reproduce and isolate the issue.

How do I start a guided debugging session to isolate a root cause?▼

To start a guided debugging session, describe the failure you are encountering. This initiates the investigative workflow to reproduce the issue, narrow its scope, and test hypotheses to isolate the root cause.

Related Skills

Explore More Software Engineering Skills→
mnthemnthe

debug

Guide systematic debugging workflows to reproduce, analyze, fix, and verify errors.

Community
Basic
adilkalamadilkalam
2

linter-loop-limits

Enforce a three-strike cap on iterative linter-fix loops.

Community
Basic
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced
hotyanovichahotyanovicha

test

Run Playwright tests with file, browser, and debug options.

Community
Basic