investigate

Investigate codebase problems read-only and produce an investigation report.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/gioe/python-libs --skill investigate-gioe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/gioe/python-libs/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/gioe/python-libs --skill investigate-gioe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This step-by-step investigation helps identify the scope of a problem in a codebase and produce an honest assessment without making any changes. It enforces plan-mode for read-only analysis and keeps cost tracking visible from start to finish.

Core Features & Use Cases

  • Read-only problem scoping: gather context, backlog, pillars, and related areas without modifying the codebase.
  • Structured investigation: explore affected files, root causes, side effects, and potential remediation approaches; produce an investigation report with decision criteria filters and actionable outcomes.
  • Cost-aware workflow: track start and finish times, backlog coverage, and whether remediation tasks are warranted; optionally propose deferred items for future work.

Quick Start

Describe the problem you want scoped, then switch to plan mode to begin a read-only investigation.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I scope a codebase problem without modifying any files?

Scoping a codebase problem without modifications requires read-only analysis that gathers context from backlogs and pillars to identify root causes. This enforces plan-mode exploration to assess affected files and document outcomes without altering the codebase.

What is the best way to investigate root causes in a codebase before deciding on remediation?

Investigating root causes before remediation involves exploring affected files, side effects, and potential approaches to produce an honest assessment. A structured investigation report outlines actionability and backlog coverage to determine whether remediation tasks are warranted.

How do I document an investigation report for a software engineering issue?

Documenting an investigation report requires outlining affected areas, root causes, actionability, and backlog coverage. The report delivers decision criteria filters and actionable outcomes, optionally proposing deferred items for future work while tracking start and finish times.

Can I assess backlog coverage during a read-only codebase analysis?

Yes, you can assess backlog coverage during a read-only codebase analysis by examining the backlog, pillars, and related areas. This read-only exploration determines whether action is needed and whether existing backlog items already cover the identified problem scope.

When should I not use a read-only investigation approach for a codebase problem?

You should not use a read-only investigation when immediate code modifications or runtime fixes are required. This approach limits analysis to context gathering and scoping, meaning it will not resolve the issue directly but only produces an assessment report for future action.