Find agent skills by outcome

- Record the indexing run metadata (duration

files scanned

- Surface files with no test coverage

no documentation

- Detect high-risk files by cross-referencing change frequency

bug-fix commits

- Catalog external dependencies with version constraints

license types

- Identify circular dependencies

tightly coupled modules

- Annotate each entry point and boundary with its file path

purpose

- Identify shared libraries

utility packages

- Record total file count

total line count

- Locate application entry points by scanning for main functions

server bootstrap files

- Catalog configuration files (environment configs

CI/CD pipelines

- Detect monorepo structures by locating workspace configurations

multiple package manifests

- Build a hierarchical directory tree capturing folder depth

file counts

- Identify the framework

language

- If the index is fresh and no structural drift is detected

confirm validity and halt; otherwise proceed to full re-indexing.

- Log the staleness assessment with specific metrics (days since update

commit count

- Identify whether major structural changes (new directories

deleted modules

- Generate compressed

token-efficient index documents in both Markdown and JSON schema formats for downstream agent consumption.

- Detect change hotspots by analyzing recent commit activity

file churn rates

- Graph dependency relationships between modules

packages

- Identify entry points

service boundaries

Productivity

- Treat every requirement below as an explicit

trackable task.

Productivity

- Assign each task a stable ID (e.g.

TASK-1.1) and use checklist items in outputs.

Repository Indexer Agent Role

# Repository Indexer

- [ ] Facts

interpretations