force-reindex

Rebuild the entire codebase search index in a background process.

11|3|Updated Jan 29, 2026

Search Tags:#automation #indexing #codebase #search #mcp #maintenance

Ready to run

npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill force-reindex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: force-reindex
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/tea-rags/skills/force-reindex
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill force-reindex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves issues with stale or corrupted search indices by performing a complete, background rebuild of the codebase index without interrupting current search availability.

Core Features & Use Cases

Zero-Downtime Rebuild: Creates a new versioned collection in the background while the current index remains active for search queries.
Atomic Switching: Automatically swaps to the new index once the background process completes successfully.
Use Case: Use this when you have performed significant refactoring or added large amounts of new code that the current index is failing to represent accurately.

Quick Start

Ask the agent to force a full re-index of the current project directory to ensure the search index is completely up to date.

Frequently Asked Questions about force-reindex

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

FAQPage Schema

How do I rebuild a codebase search index without downtime?▼

To rebuild a codebase search index without downtime, a background subagent constructs a new versioned collection while the current index remains active, executing an atomic swap only after the rebuild finishes successfully.

When should I force a full re-index of my codebase?▼

You should force a full re-index of your codebase when incremental updates are insufficient or the index state is inconsistent, which typically happens after significant refactoring or adding large amounts of new code.

How does zero-downtime re-indexing work in the background?▼

Zero-downtime re-indexing works by building a new versioned collection in a background process, maintaining continuous service availability for search queries until the new index is ready for an automatic atomic switch.

Does forcing a full codebase re-index interrupt current search availability?▼

Forcing a full codebase re-index does not interrupt current search availability because the rebuild process occurs entirely in the background, keeping the active index available for queries until the atomic swap.

Do I need explicit confirmation to perform a zero-downtime re-index?▼

Yes, you need explicit user confirmation to initiate the zero-downtime re-index, ensuring intentional execution before the background subagent begins rebuilding the entire codebase search index.