codebase-index

Generate relationship and dependency maps for component-based codebases.

62|8|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/cris-achiardi/claude-skills --skill codebase-index-cris-achiardi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-index
Source: https://github.com/cris-achiardi/claude-skills/tree/main/.claude/skills/codebase-index
Command: npx skills add https://github.com/cris-achiardi/claude-skills --skill codebase-index-cris-achiardi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Indexing codebases to automatically generate relationship and dependency maps, helping teams understand component usage, imports, utilities, and data flows without manual digging.

Core Features & Use Cases

  • Framework-agnostic analysis across React, Vue, Svelte, Astro, Next.js, Angular, and Solid with auto-detection of the project framework.
  • Generates comprehensive relationship maps including component usage, imported dependencies, utilities, and data queries.
  • Outputs in TOON by default (with JSON as an option) under an .ai folder for AI-friendly consumption and tooling compatibility.

Quick Start

Run the index_codebase.py script on your project to produce a framework-aware codebase index in TOON format by default.

Frequently Asked Questions about codebase-index

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

FAQPage Schema
How do I automatically map component dependencies and relationships in a React or Vue codebase?

Mapping component dependencies and relationships in a React or Vue codebase is done by scanning source trees and parsing imports to generate comprehensive graphs. This Skill auto-detects your framework and outputs component usage and data flow maps.

What is the best way to generate an AI-friendly dependency graph for a Svelte or Next.js project?

Generating an AI-friendly dependency graph for Svelte or Next.js projects involves outputting parsed imports and component relationships into TOON or JSON artifacts. These artifacts are saved under an .ai folder for seamless tooling compatibility.

Does framework auto-detection work for Angular and Solid when indexing a codebase?

Framework auto-detection works for Angular and Solid when indexing a codebase. The tool automatically identifies your project's framework to accurately parse imports and map component data flows without requiring manual configuration.

Can I output codebase relationship maps in JSON format instead of TOON?

You can output codebase relationship maps in JSON format instead of the default TOON. Both formats are supported and generated under the .ai folder, providing flexibility for different AI consumption and downstream tooling requirements.

How do I index an Astro codebase to visualize data queries and utility imports?

Indexing an Astro codebase to visualize data queries and utility imports requires running the index script on your project source tree. It parses your imports and generates comprehensive relationship maps including utilities and data flows.

What limitations should I expect when generating dependency maps for component-based codebases?

Limitations when generating dependency maps for component-based codebases include reliance on static import parsing and framework auto-detection. If your project uses unsupported frameworks or dynamic imports, the generated component graphs and data flows may be incomplete.