skills.rest
salazarsebas
salazarsebasCOMMUNITY
Explore all skills by this author →
Website𝕏@salazarsebas_crGitHub

investigate

Collect evidence into structured case files for incident investigations.

9|66|Updated Oct 13, 2025
Search Tags:#workflow#evidence#investigate#bug-analysis#forensic#case-file#incident-trace
One-click install
npx skills add https://github.com/salazarsebas/Cougr --skill investigate-salazarsebas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/salazarsebas/Cougr/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/salazarsebas/Cougr --skill investigate-salazarsebas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reconstruct what's happening or what an unfamiliar area does from available evidence, then produce a structured case file that another engineer can pick up cold.

Core Features & Use Cases

  • Evidence grading and disciplined reasoning (Confirmed, Deduced, Hypothesized) to organize findings.
  • Stronghold-first approach anchored on concrete evidence, expanding outward to explore related areas.
  • Path citations and a persistent case file template to track inputs, status, and conclusions.

Quick Start

Open a new investigation for a ticket ID and start recording initial evidence using the case-file template.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I investigate a bug and document findings for a hand-off?▼

To investigate a bug for hand-off, collect evidence into a structured case file template that tracks inputs, status, and conclusions, ensuring another engineer can pick up the case cold.

What is evidence grading in incident trace analysis?▼

Evidence grading in incident trace analysis organizes findings into Confirmed, Deduced, and Hypothesized categories to apply disciplined reasoning and structure to code behavior investigations.

How do I start an investigation for an unfamiliar code area?▼

Start an unfamiliar code investigation by opening a new case file for a ticket ID, anchoring reasoning on concrete evidence strongholds, and expanding outward to explore related paths.

Can I customize the workflow steps for a bug investigation?▼

Yes, you can customize bug investigation workflow steps by defining them in the customize.toml file to adapt the evidence collection and case file generation process.

What's the best way to structure a forensic code case file?▼

The best way to structure a forensic case file is using a persistent template with path citations, evidence grading, and stronghold-based reasoning to reconstruct incidents and document conclusions.

Related Skills

Explore More Software Engineering Skills→
rbah31rbah31
5

runbook

Investigate production symptoms and generate structured incident reports from logs, metrics, and traces.

Community
Intermediate
vneseyoungstervneseyoungster
27

figma-analyzer

Extract design assets, metadata, and tokens from Figma files.

Community
Advanced
oceanbaseoceanbase
161

oceanbase-source-analysis

Extract evidence from OceanBase community source code to validate error codes and runtime behavior.

Official
Advanced
LumenWipeLumenWipe
3

investigate

Trace bugs and incidents into evidence-backed findings with graded analysis.

Official
Advanced