probe

Map codebase symbols, usages, and import graphs via static analysis.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/benediktms/overmind --skill probe-benediktms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: probe
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/probe
Command: npx skills add https://github.com/benediktms/overmind --skill probe-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly orient developers at the start of a code investigation by locating symbols, tracing usages, mapping imports, and identifying how files relate to one another.

Core Features & Use Cases

  • Symbol lookup: Find definitions and references across the codebase.
  • Usage tracing & import graph discovery: Build call relationships and module dependencies to understand touchpoints.
  • File mapping: Produce a high-level map of files and roles to answer where a piece lives and what touches it.

Quick Start

Run the probe on the current project to generate a fast, high-level map of symbols, usages, and the import graph.

Frequently Asked Questions about probe

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

FAQPage Schema
How do I map symbols and trace usages across a codebase?▼

To map symbols and trace usages across a codebase, run a static analysis reconnaissance tool to locate definitions, references, and the import graph. This generates a high-level file map for quick orientation and impact analysis.

What is codebase reconnaissance and when do I need it?▼

Codebase reconnaissance is the process of identifying how files relate by mapping symbols, usages, and import graphs. You need it at the start of a code investigation for orientation, debugging, and impact analysis.

Can I use static analysis for impact analysis on repositories of varying sizes?▼

Yes, you can apply static analysis reconnaissance to software repositories of varying sizes. It operates using local project context to produce a deterministic, non-invasive report for impact analysis.

What's the best way to generate an import graph for a local project?▼

The best way to generate an import graph for a local project is running a static reconnaissance tool that maps module dependencies and call relationships. This quickly builds a high-level map of touchpoints.

Does codebase reconnaissance modify my source files during usage tracing?▼

No, codebase reconnaissance does not modify your source files during usage tracing. It operates using local project context and static analysis to generate a deterministic, non-invasive reconnaissance report.