codebase-investigator

Trace execution flows and detect unhandled errors in codebases.

4|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/grigb/gas-prompt-library --skill codebase-investigator-grigb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-investigator
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-codebase-investigator
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill codebase-investigator-grigb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the difficulty of manually tracing complex execution flows and identifying hidden error-handling gaps in large codebases.

Core Features & Use Cases

  • Execution Flow Tracing: Maps entry points, function calls, and data transformations across modules.
  • Error Analysis: Detects unhandled promises, swallowed exceptions, and missing catch blocks.
  • Integration Mapping: Identifies external API calls, database transactions, and message queue interactions.
  • Use Case: Use this agent to audit a legacy payment module to find why intermittent failures are occurring and where error logging is missing.

Quick Start

Use the codebase-investigator skill to trace the execution flow of the user authentication module and identify any unhandled error conditions.

Frequently Asked Questions about codebase-investigator

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

FAQPage Schema
How do I trace execution flow across modules to find unhandled error conditions?

To trace execution flow, you map entry points, function calls, and data transformations across modules. This process identifies unhandled promises, swallowed exceptions, and missing catch blocks to reveal hidden error-handling gaps.

Can I audit error handling and integration points within a single-project scope?

Yes, you can audit error handling and integration points within a single-project scope. This analysis maps external API calls, database transactions, and message queue interactions to find intermittent failures.

How does deep codebase analysis detect swallowed exceptions in legacy code?

Deep codebase analysis detects swallowed exceptions by performing local file operations to comprehensively explore code. It audits error handling patterns to find missing catch blocks and unhandled promise rejections.

What's the best way to map external API calls and database transactions in a codebase?

The best way to map external API calls and database transactions is through integration mapping. This identifies interaction points across modules to trace data transformations and pinpoint where error logging is missing.

Do I need local file access to investigate codebase execution flows?

Yes, you need local file access to investigate codebase execution flows. The analysis requires local permissions to execute grep, glob, and read operations for comprehensive code exploration.

Why does intermittent failure occur in a legacy payment module and how can codebase analysis help?

Intermittent failures occur due to hidden error-handling gaps and swallowed exceptions. Codebase analysis helps by auditing the legacy payment module to trace execution flows and identify where error logging is missing.