skills.rest
tdp1999
tdp1999COMMUNITY
Explore all skills by this author →
WebsiteGitHub

investigate

Investigate bugs, refactors, performance issues, or tech debt in codebases with .context subagents.

Updated Feb 11, 2026
Search Tags:#documentation#investigation#subagents#bugs#investigate#code
One-click install
npx skills add https://github.com/tdp1999/claude-code-ctx --skill investigate-tdp1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/tdp1999/claude-code-ctx/tree/main/plugins/ctx/skills/investigate
Command: npx skills add https://github.com/tdp1999/claude-code-ctx --skill investigate-tdp1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze bugs, refactors, performance issues, or tech debt by coordinating subagents to diagnose root causes and document findings.

Core Features & Use Cases

  • Orchestrates Explore, test-runner, and build-validator subagents to reproduce and analyze issues
  • Generates a standardized investigation file at .context/investigations/inv-<name>.md with findings, root cause, and recommended approaches
  • Covers bug reproduction, performance bottlenecks, refactor assessments, and tech debt cleanup

Quick Start

Describe the issue and run the investigation flow starting with /ctx:investigate.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I investigate the root cause of a bug in my codebase?▼

To investigate a bug, this Skill coordinates subagents to reproduce and analyze the issue, then generates a standardized investigation file at .context/investigations/inv-<name>.md documenting the root cause, affected files, and reproduction steps.

Can I assess technical debt and performance bottlenecks using codebase investigations?▼

Yes, codebase investigations cover performance bottlenecks, refactor assessments, and technical debt cleanup. The process orchestrates subagents to diagnose issues and outputs a structured file with recommended approaches.

Do I need pre-configured subagents to run a codebase investigation?▼

Yes, this Skill requires a project with a .context directory and pre-configured subagents, specifically orchestrating Explore, test-runner, and build-validator subagents to execute the investigation flow.

What's the best way to document codebase findings for a complex refactor?▼

The best way to document findings is running the investigation flow, which creates a standardized .context/investigations/inv-<name>.md file. This file outlines the root cause, affected files, reproduction steps, and recommended approaches.

How do I start a guided investigation for a codebase issue?▼

You start a guided investigation by describing the issue and running the flow with the /ctx:investigate command, which triggers the subagents to begin diagnosing and documenting the problem.

What limitations exist when investigating tech debt without a .context directory?▼

Investigating tech debt requires a .context directory and pre-configured subagents; without this environment setup, the Skill cannot orchestrate the reproduction, root-cause analysis, or generate the structured investigation file.

Related Skills

Explore More Software Engineering Skills→
phucle297phucle297

cavecrew

Guide subagent delegation for code investigation, file editing, and code review.

Community
Advanced
popo0407popo0407

refactoring

Guide code refactoring with impact analysis and backward compatibility procedures.

Community
Basic
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
mazenyassergithubmazenyassergithub
6

analyze

Analyze code, architecture, bugs, performance, and security with prioritized recommendations.

Community
Advanced