gds-investigate

Investigate bugs and code areas with evidence-graded findings recorded in a structured case file.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-investigate-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-investigate
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-investigate
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-investigate-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Debugging and incident analysis often rely on guesswork, lost context, and unverified assumptions. This Skill enforces a disciplined forensic workflow that reconstructs what happened from available evidence, grades every finding as Confirmed, Deduced, or Hypothesized, and produces a persistent case file another engineer can pick up cold. ## Core Features & Use Cases - Evidence-graded investigation: Anchors analysis in a Confirmed stronghold, traces causality backward from symptoms, and records hypotheses with explicit confirm/refute criteria that are never deleted. - Structured case file output: Generates a case file from a template covering evidence inventory, timeline, backlog, source code trace, and a confidence-rated conclusion, with follow-up blocks for resuming prior investigations. - Use Case: Given a ticket ID or a log file with a stack trace, the Skill maps the evidence perimeter, traces the error origin to path:line citations, and hands off a diagnosis with a recommended next step such as a quick fix or a tracked story. ## Quick Start Ask the AI to investigate the bug described in ticket PROJ-1234 and produce an evidence-graded case file with the root cause traced to its source.

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 evidence-graded findings?

Provide a ticket ID, log file, stack trace, or problem description as input. The workflow anchors on one Confirmed piece of evidence, traces causality backward from the symptom, and records every finding with path:line citations in a structured case file.

How to resume a previous code investigation?

Pass the path to an existing case file as the input. The Skill loads it, surfaces open hypotheses, backlog items, missing evidence, and the last conclusion, then appends new work under a dated Follow-up block.

Can this investigate unfamiliar code without a reported bug?

Yes, exploration mode works without a symptom. Provide a code area name or commit range, and it maps inputs, outputs, dependencies, and control flow to build a mental model documented in the same case file format.

Does the investigation apply fixes to the code?

No, the investigation stops at the diagnosis. For trivial root causes like an off-by-one or missing null check it may suggest a one-line fix in the report, but implementation is handed off to downstream workflows.

What happens when there is not enough evidence to find a root cause?

The case is marked evidence-light, the gap is documented as a finding with what it would resolve and how to obtain it, and the backlog is populated with prioritized data-collection items before pausing for user direction.