explore-codebase

Explore repository structure and trace code relationships using a knowledge graph.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill explore-codebase-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explore-codebase
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/explore-codebase
Command: npx skills add https://github.com/islamu-ngo/Event --skill explore-codebase-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Navigating an unfamiliar codebase to find where code lives, how modules relate, or what calls a given symbol is slow and error-prone when done by manually grepping files. This Skill provides a structured workflow for answering architecture and code-location questions using a code knowledge graph. ## Core Features & Use Cases - Architecture Overview: Start from graph statistics and community detection to understand high-level module structure before drilling into details. - Symbol and Relationship Tracing: Locate functions and classes with semantic search, then trace callers, callees, and imports to understand dependencies. - Execution Flow Analysis: List and inspect execution flows to understand how code paths run end to end. - Use Case: When asked "what implements the payment retry feature", run a semantic search for the relevant symbols, then use callers_of and callees_of queries to map the full dependency chain. ## Quick Start Ask the AI to give you an architecture tour of this repository and show which modules call the authentication service.

Frequently Asked Questions about explore-codebase

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

FAQPage Schema
How do I find where a function is defined in a large codebase?▼

Use semantic_search_nodes_tool to locate the function or class by name or description, then use children_of on the containing file to see all its symbols. Start with get_minimal_context to keep token usage low.

How do I trace what calls a specific function?▼

Use query_graph_tool with the callers_of pattern to list all callers of a symbol, and callees_of to see what it invokes. The imports_of pattern reveals module-level dependencies.

What is the best way to get an architecture overview of a repository?▼

Run list_graph_stats for overall metrics, then get_architecture_overview_tool for the high-level community structure. Drill into specific modules with list_communities_tool and get_community.

When should I not use the knowledge graph exploration workflow?▼

This workflow is not suited for bug diagnosis, diff review, or refactoring tasks. It is designed for locating code and understanding structure, not for evaluating changes or fixing defects.

How do I keep graph queries token-efficient?▼

Always start with get_minimal_context before other graph tools and use detail_level="minimal" on all calls. Escalate to standard detail only when minimal output is insufficient, targeting five or fewer tool calls per task.