test-self-reindex

You can validate TeaRAGs indexing pipeline changes by running a full-scale reindex on a worktree using an isolated project alias. This ensures the main index remains untouched while verifying ingestion, codegraph, and enrichment logic end-to-end.

Testing codegraph and ingestion regressions in a TeaRAGs MCP server involves performing a self-reindex against a worktree source. The process automatically verifies enrichment health and functional search capabilities across file and chunk levels to catch regressions.

Yes, you can run a TeaRAGs reindex on a separate worktree path safely. The skill requires an absolute worktree path and indexes it as a separate project alias, ensuring your main project index remains completely untouched during validation.

To check enrichment health after modifying ingestion logic, execute a full reindex using the tea-rags CLI and MCP toolset. The validation process targets both file and chunk levels to verify end-to-end system integrity and detect functional regressions.

Your TeaRAGs enrichment pipeline needs an isolated project alias for testing to prevent indexing corruption. By aliasing the worktree separately, developers can perform non-trivial ingestion changes and verify pipeline integrity without risking the main index.