skills.rest
SakshamKandel
SakshamKandelCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Guide root-cause analysis through investigate, analyze, hypothesize, and implement phases.

Updated Apr 24, 2026
Search Tags:#debugging#troubleshooting#analysis#investigate#root-cause#bug#gstack
One-click install
npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill investigate-sakshamkandel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/investigate
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill investigate-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging and root-cause investigation to prevent blind fixes and recurring issues.

Core Features & Use Cases

  • Structured four-phase workflow: investigate, analyze, hypothesize, implement.
  • Guardrails to surface prior investigations and learnings, and align fixes to root causes.
  • Use Case: When a fault is reported, trace the underlying cause, validate hypotheses, and implement minimal, verified improvements.

Quick Start

Initiate a root-cause analysis on the current bug and outline the four-phase plan (investigate, analyze, hypothesize, implement) to guide the fix.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I perform root-cause debugging on a software bug?▼

Root-cause debugging requires a structured four-phase workflow: investigate the fault, analyze the findings, hypothesize the fix, and implement the verified improvement to prevent recurring issues.

What is the best way to trace the underlying cause of a performance regression?▼

Tracing a performance regression involves enforcing root-cause analysis before applying fixes, validating hypotheses against codebase behavior, and implementing minimal verified improvements to resolve the fault.

Can I use structured analysis for troubleshooting errors across deployments?▼

Yes, structured analysis applies to software bugs, errors, and performance regressions across codebases, services, and deployments, guiding you through investigation and implementation phases.

How do I prevent blind fixes when investigating a reported fault?▼

Preventing blind fixes requires using guardrails to surface prior investigations and learnings, aligning fixes directly to root causes, and validating hypotheses before implementing changes.

Does root-cause analysis integrate with gstack context for prior investigations?▼

Yes, root-cause analysis integrates with gstack context to surface prior investigations and learnings, providing guardrails that align your current debugging workflow to validated root causes.

Related Skills

Explore More Software Engineering Skills→
cloudofgeorgecloudofgeorge

canary

Monitors deployed apps for errors, performance regressions, and page failures via screenshots and baselines.

Community
Advanced
JackSmack1971JackSmack1971

debug-root-cause-analysis

Guide structured root-cause debugging through observe, reproduce, hypothesize, test, fix, verify, and prevent phases.

Community
Advanced
kiran-capoor94kiran-capoor94
1

code-review

Review code changes using task context and six analysis lenses.

Community
Advanced
duongbui234duongbui234

systematic-debugging

Systematizes software debugging via Investigation, Analysis, Hypothesis, Implementation phases.

Community
Advanced