gds-investigate

Investigates bugs and code areas into evidence-graded forensic case files.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-investigate-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-investigate
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-investigate
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-investigate-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Debugging and code exploration often rely on guesswork and lose context across sessions. This Skill reconstructs what happened from available evidence, grades every finding as Confirmed, Deduced, or Hypothesized, and persists everything in a structured case file another engineer can pick up cold. ## Core Features & Use Cases - Evidence-graded investigation: Anchors on one Confirmed piece of evidence (a stronghold), traces causality backward from symptoms or outputs, and records hypotheses with explicit confirm/refute criteria that are never deleted. - Persistent case files: Initializes a Markdown case file from a template covering evidence inventory, timeline, backlog, source code trace, and a confidence-rated conclusion, with follow-up blocks for multi-session work. - Dual-mode calibration: Handles symptom-driven defect chasing (tickets, logs, stack traces) and symptom-free code area exploration with the same disciplined workflow. - Use Case: Given a ticket ID and a log file, the Skill maps the evidence perimeter, traces the error to its origin with path:line citations, and hands off a final report with fix direction and reproduction plan. ## Quick Start Ask the AI to investigate the bug described in ticket PROJ-1234 using the attached error log and produce an evidence-graded case file.

Frequently Asked Questions about gds-investigate

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

FAQPage Schema
How do I investigate a bug with structured evidence tracking?

Provide a ticket ID, log file, stack trace, or problem description. The Skill anchors on one Confirmed piece of evidence, traces causality backward, and records every finding in a persistent case file with confidence grades.

How to explore unfamiliar code before making changes?

Name the code area without any symptom. The Skill maps I/O, control flow, and dependencies, then builds an area model in the case file with a verification plan instead of a root-cause conclusion.

Can an investigation resume across multiple sessions?

Yes. Passing a path to an existing case file resumes it: open hypotheses, backlog items, missing evidence, and the last conclusion are surfaced, and new work appends under a dated Follow-up block.

What happens when there is not enough evidence to diagnose?

The case is marked evidence-light, the backlog is filled with prioritized data-collection items, and the missing evidence is documented with its impact and how to obtain it. The Skill pauses rather than guessing.

Does the investigation also implement the fix?

No. The workflow stops at diagnosis with a fix direction and reproduction plan. Implementation is routed to follow-up workflows such as quick-dev or a tracked story, keeping investigation and change separate.