Investigation Patterns

Name: Investigation Patterns
Availability: InStock
Author: motoki317

Generate evidence-based reports through a phased workflow for codebase investigation.

4|Updated Oct 20, 2025

Search Tags:#metrics #patterns #debug #evidence #investigate #code #analyze

Ready to run

npx skills add https://github.com/motoki317/dotfiles --skill investigation-patterns-motoki317

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Investigation Patterns
Source: https://github.com/motoki317/dotfiles/tree/main/.claude/skills/investigation-patterns
Command: npx skills add https://github.com/motoki317/dotfiles --skill investigation-patterns-motoki317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, evidence-based approach to analyzing codebases, diagnosing issues, and identifying patterns without guessing.

Core Features & Use Cases

Structured evidence collection: Guidelines to gather file:line references, confidence metrics, and a clear scope.
Phased investigation workflow: Scope Classification, Evidence Collection, Synthesis with Metrics, and Debugging Workflow to ensure thorough analysis.
Use cases: Troubleshoot bugs, understand unfamiliar codebases, validate design decisions, and perform root-cause analysis.

Quick Start

Start by applying the investigation workflow to a sample project to generate an evidence-based report.

Frequently Asked Questions about Investigation Patterns

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

FAQPage Schema

What is an evidence-based approach to debugging code?▼

An evidence-based approach to debugging code relies on gathering concrete file:line references and confidence metrics instead of guessing. It provides a structured workflow to systematically collect proof, synthesize findings, and perform rigorous root-cause analysis.

How do I systematically analyze an unfamiliar codebase?▼

To systematically analyze an unfamiliar codebase, apply a phased investigation workflow: classify the scope, collect evidence with file:line references, synthesize metrics, and follow a structured debugging workflow to validate design decisions and understand architecture without guessing.

What's the best way to investigate root-cause issues in software?▼

The best way to investigate root-cause issues is using a deterministic, phase-driven workflow that prioritizes structured evidence collection and metrics-driven synthesis. This ensures thorough analysis and yields actionable debugging guidance for troubleshooting bugs.

Can I use a phased investigation workflow for architecture validation?▼

Yes, you can use a phased investigation workflow for architecture validation. The approach is applicable across architecture, implementation, and design tasks, providing metrics-driven synthesis to rigorously verify design decisions within a defined scope.

How do I collect evidence when troubleshooting bugs?▼

To collect evidence when troubleshooting bugs, follow structured guidelines to gather specific file:line references, assign confidence metrics to findings, and define a clear investigation scope. This ensures a rigorous, verifiable debugging process.