skills.rest
ajsai47
ajsai47COMMUNITY
Explore all skills by this author →
WebsiteGitHub

investigate

Investigate software bugs through a four-phase root cause workflow.

11|2|Updated Mar 31, 2026
Search Tags:#debugging#root cause#error analysis#regression testing#bug investigation#systematic debugging
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill investigate-ajsai47
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/team/investigate
Command: npx skills add https://github.com/ajsai47/holyclaude --skill investigate-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging often devolves into guessing and patching symptoms, which creates recurring bugs and wasted effort. This Skill enforces a disciplined root cause investigation process so you fix the actual problem instead of playing whack-a-mole.

Core Features & Use Cases

  • Four-Phase Investigation Workflow: Systematically moves through investigate, analyze, hypothesize, and implement phases with mandatory evidence gathering before any fix is written.
  • Scope Lock & Safety Guardrails: Automatically restricts code edits to the affected module to prevent accidental changes elsewhere, with clear freeze and unfreeze controls.
  • Pattern Matching & Learnings: Checks bugs against known failure patterns, searches prior session learnings for similar issues, and enforces a 3-strike rule to stop unproductive guessing.
  • Use Case: When your staging environment throws a cryptic 500 error and git log shows recent changes to the auth module, this Skill guides you to trace the exact code path, verify the root cause with temporary instrumentation, and write a regression test before applying the minimal fix.

Quick Start

Use the investigate skill to debug the 500 error on the checkout page by first gathering the error logs and recent git changes before proposing any fix.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I stop debugging from becoming a guessing game?▼

To debug a software regression, gather error logs and recent git changes to trace the exact code path, verify the root cause with temporary instrumentation, write a regression test, and apply a minimal fix scoped only to the affected module.

How do I debug a cryptic 500 error after recent codebase changes?▼

To debug a 500 error, gather error logs and recent git changes to trace the exact code path, verify the root cause with temporary instrumentation, write a regression test, and apply a minimal fix scoped only to the affected module.

Can I restrict code edits to the affected module during bug investigation?▼

Yes, scope locking restricts code edits to the affected module during bug investigation, preventing accidental changes elsewhere with clear freeze and unfreeze controls for safety guardrails.

When should I use a systematic debugging workflow instead of quick fixes?▼

The best way to prevent recurring bugs is enforcing a root cause investigation process that checks bugs against known failure patterns, enforces a 3-strike rule to stop guessing, and mandates regression test creation before fixes.

Related Skills

Explore More Software Engineering Skills→
gil-kapelgil-kapel
2

debug-fix-agent

Analyze error logs and stack traces to guide minimal code fixes.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
Donaldshen27Donaldshen27

systematic-debugging

Identify bug root causes through a four-phase systematic debugging framework.

Community
Advanced
gmliaogmliao
1

systematic-debugging

Guide systematic debugging through root-cause investigation, pattern analysis, hypothesis testing, and implementation.

Community
Advanced