skills.rest
rioX432
rioX432COMMUNITY
Explore all skills by this author →
Website𝕏@rioX432GitHub

dev-investigate

Investigate codebase issues in a forked context and produce a report with file:line references.

2|1|Updated Mar 16, 2026
Search Tags:#debugging#investigation#codebase analysis#test coverage#git history#dependency tracing
One-click install
npx skills add https://github.com/rioX432/live-translate --skill dev-investigate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-investigate
Source: https://github.com/rioX432/live-translate/tree/main/.claude/skills/dev-investigate
Command: npx skills add https://github.com/rioX432/live-translate --skill dev-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps investigate codebase issues thoroughly without polluting the main context, making it easier to trace bugs, understand architecture, and gather evidence before changing code.

Core Features & Use Cases

  • Forked-context analysis: Runs investigation work in isolation so large file reads stay out of the caller’s context.
  • Codebase tracing: Finds likely entry points, follows data flow, and maps dependencies across relevant files.
  • Test and history review: Checks existing tests, recent changes, and blame history to build a grounded understanding of the issue.
  • Use case: Use it when you need a structured pre-fix investigation report for a bug, regression, or unclear behavior in a repository.

Quick Start

Ask the skill to investigate the issue using the key symptoms, acceptance criteria, and any known affected areas.

Frequently Asked Questions about dev-investigate

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

FAQPage Schema
How do I investigate codebase issues without polluting my main context window?▼

Forked-context codebase investigation isolates large file reads and tracing operations in a separate context, keeping your main conversation clean while mapping dependencies and gathering bug evidence.

What is the best way to trace bugs and map dependencies before changing code?▼

Codebase tracing for bug investigation finds entry points, follows data flow, and maps dependencies across relevant files to build a grounded understanding of the issue before applying fixes.

Does git history and test coverage review help with debugging regressions?▼

Git history and test coverage review check existing tests, recent changes, and blame history to provide grounded evidence for debugging regressions or unclear repository behavior.

Can I get a structured investigation report with file and line references for a bug?▼

A structured pre-fix investigation report provides self-contained documentation with file:line references, ensuring you have clear evidence and traced dependencies before modifying code.

What do I need to provide to start a codebase debugging investigation?▼

To start a codebase debugging investigation, provide key symptoms, acceptance criteria, and any known affected areas so the skill can read CLAUDE.md and trace relevant entry points.

When should I not use an isolated investigation approach for repository debugging?▼

Avoid isolated investigation when you need immediate inline fixes without evidence gathering, as this approach focuses on producing comprehensive pre-fix reports rather than direct code modifications.

Related Skills

Explore More Software Engineering Skills→
gioegioe

investigate

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

Community
Advanced
xg-gh-25xg-gh-25
36

code-review

Review PRs, branches, or files with file:line references.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
frankxaifrankxai
6

arcanea-systematic-debug

Diagnose and fix software bugs through systematic hypothesis testing and prevention.

Community
Advanced