reindex

Scan source files and generate docs/codebase-index.json.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill reindex-artemiopadilla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reindex
Source: https://github.com/ArtemioPadilla/agent-triforce/tree/main/.claude/skills/reindex
Command: npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill reindex-artemiopadilla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rebuilds the codebase knowledge index across the repository to improve searchability and traceability.

Core Features & Use Cases

  • Scans src/ recursively to collect module structure, exports, imports, and dependencies.
  • Builds a dependency graph and flags tech-debt hotspots for remediation.
  • Keeps docs/codebase-index.json in sync for engineering teams.

Quick Start

Run the reindex operation to generate or refresh docs/codebase-index.json and verify consistency.

Frequently Asked Questions about reindex

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

FAQPage Schema
How do I rebuild the codebase knowledge index after source file changes?

To rebuild the codebase knowledge index, run a reindex operation that recursively scans src/ to collect module structure, exports, imports, and dependencies, then refreshes docs/codebase-index.json to keep it synchronized with your latest codebase.

What is codebase indexing and how does a dependency graph improve searchability?

Codebase indexing scans source files to map module structure, imports, and exports into a dependency graph, storing the results in docs/codebase-index.json to improve codebase searchability and traceability across engineering teams.

Do I need an existing docs/codebase-index.json file to reindex my source files?

Yes, the reindex operation requires an existing docs/codebase-index.json file and access to the src/ directory to validate and update the dependency graph against your current codebase.

Can I flag tech-debt hotspots while scanning src/ for module dependencies?

Yes, reindexing scans src/ recursively to build a dependency graph and automatically flags tech-debt hotspots for remediation by validating the updated index against TECH_DEBT.md when present in the repository.

What's the best way to keep docs/codebase-index.json in sync across development teams?

The best way to keep docs/codebase-index.json in sync is running a reindex operation that scans source files, updates module dependencies, and validates consistency against TECH_DEBT.md and reviews when present in the repository.

Why is my codebase index out of date after adding new modules to src/?

Your codebase index is out of date because docs/codebase-index.json was not refreshed after adding new modules, requiring a reindex operation to scan src/ and rebuild the dependency graph for the new codebase structure.