skills.rest
mkalkere
mkalkereCOMMUNITY
Explore all skills by this author →
GitHub

repo-indexing

Index repository structure and dependencies into file_inventory.yaml and import_graph.yaml.

4|Updated Feb 1, 2026
Search Tags:#indexing#codebase#dependencies#analysis#patterns#repository#memory
One-click install
npx skills add https://github.com/mkalkere/agent-coordinator --skill repo-indexing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-indexing
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/core/repo-indexing
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill repo-indexing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Index repositories to maintain an always-current view of codebases for faster understanding, automated reasoning, and better impact analysis.

Core Features & Use Cases

  • Build a comprehensive file inventory, dependency graph, and test mappings to support impact analysis and onboarding.
  • Keep track of code patterns, anti-patterns, and potential issues to improve code health and maintainability.
  • Use cases: onboarding new developers, planning changes, and automated code understanding tasks.

Quick Start

Run the index_repo tool to build or refresh a complete repository index.

Frequently Asked Questions about repo-indexing

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

FAQPage Schema
How do I index a repository structure and dependencies for codebase analysis?▼

To index a repository structure, you run the index_repo tool to build a comprehensive file inventory and dependency graph. This generates artifacts like file_inventory.yaml and import_graph.yaml in agent memory for ongoing codebase analysis.

What's the best way to analyze codebase impact after changes across large projects?▼

Analyzing codebase impact after changes relies on repository indexing to maintain an always-current view of your project. It maps file dependencies and test relationships so you can assess downstream impact accurately across large codebases.

Does repository indexing automatically exclude directories like node_modules and .venv?▼

Yes, repository indexing honors configured exclusions such as .venv, node_modules, and __pycache__. These directories are skipped during the indexing process to maintain performance and avoid indexing third-party dependencies.

Can I perform incremental indexing instead of a full repository scan?▼

Yes, repository indexing supports both incremental and full indexing modes. Incremental indexing refreshes the existing repository index to reflect recent changes without rebuilding the entire file inventory and import graph from scratch.

How do I generate a dependency graph for onboarding new engineers?▼

Generating a dependency graph for onboarding involves running the repository indexer, which outputs an import_graph.yaml artifact. This maps codebase dependencies and patterns to help new engineers understand project structure and relationships quickly.

Related Skills

Explore More Software Engineering Skills→
Sounder25Sounder25
27

Clean Build Artifacts

Remove common build artifact folders with optional dry-run preview.

Community
Basic
miptah21miptah21
2

tracing-downstream-lineage

Trace downstream table and DAG dependencies to generate change impact reports.

Community
Intermediate
CristoVenturesCristoVentures
2

pattern-recognition-specialist

Identify design patterns, anti-patterns, and code quality issues across codebases.

Official
Advanced
linenoizelinenoize
1

recon

Map codebase structure, dependencies, and conventions for downstream agent tasks.

Community
Advanced