skills.rest
joi-fairshare
joi-fairshareCOMMUNITY
Explore all skills by this author →
GitHub

rootCause

Investigate reproducible software errors with four-phase debugging and module boundary enforcement.

1|2|Updated Mar 19, 2026
Search Tags:#debugging#investigation#analysis#reporting#root-cause#module-boundary
One-click install
npx skills add https://github.com/joi-fairshare/agentic-workflow --skill rootcause
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rootCause
Source: https://github.com/joi-fairshare/agentic-workflow/tree/main/skills/rootCause
Command: npx skills add https://github.com/joi-fairshare/agentic-workflow --skill rootcause

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill keeps debugging scoped and structured so you can turn a vague failure report into a verified root cause without spilling fixes across unrelated folders.

Core Features & Use Cases

  • Phase-driven workflow: Investigate the failure, analyze call chains, hypothesize causes, and implement within a four-phase loop that captures evidence and decisions.
  • Module boundary freeze: Identify the smallest logical module or namespace and declare it as the scope for all fixes, preventing scope creep.
  • Documentation & reporting: Capture hypotheses, interventions, verification status, and the final investigation report under ~/.agentic-workflow/<repo>/investigations for auditability.

Quick Start

Use /rootCause followed by the error message to reproduce the failure, map the call chain, and log the investigation report.

Frequently Asked Questions about rootCause

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

FAQPage Schema
How do I debug reproducible software errors without causing scope creep across unrelated folders?▼

Debug reproducible software errors using a structured four-phase workflow that freezes fixes to a specific module boundary, preventing scope creep across unrelated folders while tracing the call chain.

What is the best way to trace a call chain and find the root cause of a failure?▼

The best way to find a root cause is applying a phase-driven workflow that investigates the failure, analyzes the call chain, and logs hypotheses before freezing the fix to the smallest logical module.

How do I document debugging hypotheses and fix attempts for auditability?▼

Document debugging hypotheses and fix attempts by saving a final investigation report under the ~/.agentic-workflow/<repo>/investigations directory, satisfying traceability and auditability expectations.

Can I use a structured debugging workflow to investigate errors within a specific code repository?▼

Yes, you can investigate errors within a code repository by applying a structured debugging workflow that reproduces failures, maps call chains, and enforces module boundaries before implementing fixes.

Why does my debugging process lack traceability when fixing vague failure reports?▼

Your debugging lacks traceability because hypotheses and fix attempts are not logged. Capturing evidence and saving an investigation report under ~/.agentic-workflow/<repo>/investigations ensures auditability.

Related Skills

Explore More Software Engineering Skills→
yale-som-hpcyale-som-hpc
5

starting-a-new-project

Create a reproducible project skeleton with code, data, and logs on the Yale HPC cluster.

Official
Intermediate
VrooliVrooli
54

Agent Manager Process Investigation Apply

Apply prioritized investigation report fixes to resume agent-manager runs.

Official
Advanced
d-o-hubd-o-hub
11

test-fix

Diagnose and fix failing Rust tests with cargo test variations.

Community
Basic
Himanshu040604Himanshu040604

sentry-go-sdk

Integrate the Sentry Go SDK for error tracking, tracing, and logging.

Community
Intermediate