sj-investigate

Enforce evidence-based root cause analysis with a structured 7-step workflow.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/s0613/S-skills --skill sj-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sj-investigate
Source: https://github.com/s0613/S-skills/tree/main/skills/sj-investigate
Command: npx skills add https://github.com/s0613/S-skills --skill sj-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the common pitfall of developers making quick, speculative fixes that only mask bug symptoms instead of addressing the actual root cause, which leads to recurring issues and wasted development time.

Core Features & Use Cases

  • Structured 7-Step Workflow: Enforces a standardized process from problem intake and data collection to hypothesis validation, root cause confirmation, and fix planning.
  • Evidence-Based Guardrails: Requires concrete proof to confirm or refute all hypotheses before any code modifications are allowed, preventing unproven changes.
  • Knowledge Accumulation: Automatically logs investigation patterns and root causes to a shared log for faster resolution of similar bugs in future sessions.
  • Use Case: When a production bug causes unexpected user behavior, use this skill to trace the full data flow, validate potential causes, and identify the exact root issue without making risky unproven changes.

Quick Start

Use the sj-investigate skill to trace the root cause of the unexpected payment processing failure reported by users this morning.

Frequently Asked Questions about sj-investigate

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

FAQPage Schema
How do I find the root cause of a production bug instead of just fixing the symptoms?

Root cause debugging requires a structured 7-step workflow that enforces evidence-based hypothesis validation. It traces full data flow and demands concrete proof to confirm potential causes before any code modifications are allowed.

What is evidence-based hypothesis validation in software troubleshooting?

Evidence-based hypothesis validation is a debugging guardrail requiring concrete proof to confirm or refute potential causes before implementing fixes. It prevents unproven code changes that mask bug symptoms and lead to recurring issues.

How do I trace error data flow for unexpected backend behavior?

Tracing error data flow involves systematically collecting data, validating hypotheses against concrete evidence, and confirming the exact root issue. This structured investigation prevents risky unproven changes during production bug resolution.

Can I use systematic debugging for full-stack and web application errors?

Systematic debugging applies to all software debugging scenarios including web, backend, and full-stack applications. It enforces a standardized process from problem intake and data collection to root cause confirmation and fix planning.

What is the best way to document bug investigation patterns for future sessions?

Documenting bug investigation patterns involves automatically logging root causes and analysis steps to a shared log. This knowledge accumulation enables faster resolution of similar bugs in future debugging sessions.