investigate

Trace dependencies and analyze codebase areas affected by a requested topic.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill investigate-lleontor705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/investigate
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill investigate-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase analysis and bug diagnosis at scale, enabling engineers to map dependencies, compare approaches, and plan fixes.

Core Features & Use Cases

  • Structured analysis: Systematically reads files, traces dependencies, and documents findings.
  • Approach comparison: Provides multiple architectural options with effort/risk tradeoffs.
  • Evidence-backed diagnosis: Traces root causes with evidence chains and recommended fixes.

Quick Start

Provide a structured investigation plan and diagnostic results for a given topic.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I investigate a codebase for architecture decisions and migration assessments?

Codebase investigation for architecture decisions and migration assessments systematically inspects source files, traces dependency paths, and scopes impact across multi-module repositories to deliver evidence-backed recommendations.

What is the best way to trace root causes for bugs in multi-module repositories?

Tracing root causes in multi-module repositories requires building evidence chains through source inspection and dependency review to isolate faults and document clearly scoped recommended fixes.

How does path tracing work when analyzing dependencies across a codebase?

Path tracing during codebase analysis works by inspecting source files to map execution routes and dependency links, providing a structured view of how modules interact and where requested topics impact the system.

Can I compare architectural approaches and evaluate effort tradeoffs during a codebase migration?

Yes, codebase migration analysis compares multiple architectural approaches by reviewing source dependencies and tracing paths, providing structured options that weigh effort and risk tradeoffs for planning fixes.

Does codebase investigation work for debugging and diagnosing issues at scale?

Yes, codebase investigation works for debugging at scale by systematically reading files and tracing dependencies to map impact, enabling engineers to diagnose issues and plan fixes across complex multi-module repositories.