Project Indexing

Index polyglot codebases into a standardized .claude/.project-index.json file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/qenex-ai/project-context-manager --skill project-indexing-qenex-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Project Indexing
Source: https://github.com/qenex-ai/project-context-manager/tree/main/skills/project-indexing
Command: npx skills add https://github.com/qenex-ai/project-context-manager --skill project-indexing-qenex-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Analyze and index polyglot codebases to surface language makeup, dependencies, and project structure.

Core Features & Use Cases

  • Detect languages, manifests, and entry points across Python, Rust, Go, Julia, Elixir, C++, Zig, and JavaScript/TypeScript.
  • Generate a unified .claude/.project-index.json index with language breakdown, dependencies, key files, and structural metadata.
  • Enable quick project onboarding, auditing, and planning for refactors in multi-language repos.

Quick Start

Run the project-indexing workflow on a repository to produce a machine-readable index.

Frequently Asked Questions about Project Indexing

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

FAQPage Schema
How do I index a polyglot codebase to surface language makeup and dependencies?

To index a polyglot codebase, run the project-indexing workflow to scan manifests and entry points across Python, Rust, Go, and JavaScript/TypeScript, generating a unified .claude/.project-index.json file with structural metadata.

Can I detect project structure and entry points across Python, Rust, Go, Julia, and Elixir?

Yes, you can detect project structure and entry points across Python, Rust, Go, Julia, Elixir, C++, Zig, and JavaScript/TypeScript by scanning the repository to identify manifests and key files.

What is the best way to audit dependencies in a multi-language repository?

The best way to audit dependencies in a multi-language repository is to generate a standardized .claude/.project-index.json index that surfaces language breakdowns and manifest data for quick analysis.

Does project indexing work with C++, Zig, and JavaScript/TypeScript repos for planning refactors?

Project indexing works with C++, Zig, and JavaScript/TypeScript repos by extracting architecture, structure, and git data to enable quick planning for cross-language refactors.

How do I onboard a new multi-language repo quickly using a generated index?

You can onboard a new multi-language repo quickly by running the indexing workflow to produce a machine-readable .claude/.project-index.json file containing architecture, manifests, and entry points.

What format does the project index output use for architecture and git data?

The project index output uses a standardized .claude/.project-index.json format that contains architecture, structure, manifests, entry_points, and git data for the analyzed codebase.