kitty:explore

Construct a navigable graph of modules, imports, definitions, and relationships.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Kakise/cartographing-kitties-plugin --skill kitty-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kitty:explore
Source: https://github.com/Kakise/cartographing-kitties-plugin/tree/main/plugins/kitty/skills/kitty-explore
Command: npx skills add https://github.com/Kakise/cartographing-kitties-plugin --skill kitty-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structural codebase exploration and understanding of code organization, definitions, imports, and relationships using a graph-based view. It helps you quickly answer questions like which module defines a symbol, how files are related, and what depends on a component.

Core Features & Use Cases

  • Browse definitions, imports, and relationships through graph traversal
  • Inspect project structure, modules, and dependencies
  • Identify call graphs and inheritance relationships to understand code flow

Quick Start

Ask it to explore a file or module to view its definitions, imports, and relationships.

Frequently Asked Questions about kitty:explore

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

FAQPage Schema
How do I explore codebase structure and understand file relationships quickly?

You can explore codebase structure by constructing a graph-based model that maps modules, imports, definitions, and relationships, allowing you to quickly understand how a project is organized and how files relate to each other.

How do I find what depends on a specific symbol or component in my code?

To find what depends on a specific symbol, you traverse the graph-based representation of your code to identify call graphs and inheritance relationships, surfacing exactly what relies on that component within the project.

Can I visualize call graphs and inheritance relationships to understand code flow?

Yes, you can identify call graphs and inheritance relationships by traversing the navigable graph representation built from the codebase, which clarifies the structural code flow and component dependencies.

What's the best way to identify which module defines a specific symbol?

The best way to identify which module defines a symbol is to browse the codebase's definitions through graph traversal, which surfaces the exact module and file containing the target definition.

Does graph-powered code exploration work for understanding imports across a project?

Yes, graph-powered code exploration works for understanding imports by inspecting the project structure and mapping dependencies, allowing you to browse definitions, imports, and relationships across the entire codebase.