Indexes or re-indexes the current project into the OpenTrace knowledge graph using opentraceai. Supports path/flags; reports results and graph stats.
From opentrace-ossnpx claudepluginhub opentrace/opentrace --plugin opentrace-oss/indexGenerates project documentation, knowledge base, API docs, structure analysis, or README for a target path. Supports --type (docs|api|structure|readme) and --format (md|json|yaml).
/indexIndexes codebase into Supermemory for persistent context: detects tech ecosystem, scans manifests/configs/entry points/architecture.
/indexScans codebase for components (controllers, services, models) and external resources to generate searchable specs in specs/.index/. Supports --path, --type, --exclude, --dry-run, --force, --changed, --quick flags.
/indexGenerates AI-readable feature index mapping natural language descriptions of UI elements, interactions, and business flows to exact code locations and modification guides. Saves markdown report to .claude/context/index.md.
/indexGenerates project documentation (docs, API, structure, readme) and knowledge base for a target directory in MD, JSON, or YAML format with update option.
/indexIndexes a folder of documents for semantic search: scans supported files, extracts text, stores embeddings in local vector database. Reports files indexed, skipped, and errors.
Index the current project into the OpenTrace knowledge graph so that agents and skills can query it.
$ARGUMENTS
Determine the target path: If the user provided a path in the arguments, use that. Otherwise default to the repository root (find it with git rev-parse --show-toplevel).
Run the indexer: Change directory to the target path and run the indexer. This ensures the .opentrace/ directory is created in the right place.
cd <path> && uvx opentraceai index .
Use --verbose if the user asked for verbose/debug output. Pass through any other flags the user specified (e.g. --db, --repo-id, --batch-size).
Report results: After the command completes, summarize what was indexed. If the command fails, show the error and suggest fixes (e.g. missing uv or dependencies, wrong path).
Verify: Run uvx opentraceai stats (passing the same --db flag if the user provided one) to show the updated graph contents so the user can confirm the index looks right.