What problem does it solve? Changing RAG configuration files without knowing the re-indexing impact leads to either wasted compute on unnecessary full rebuilds or stale indexes that silently return wrong results. This Skill provides a decision matrix that classifies each config change before you edit anything. ## Core Features & Use Cases - Change Classification Matrix: Maps edits to rag-config.yaml, metadata-rules.yaml, multilingual-glossary.yaml, queries.yaml, and chunker/embedder settings to query-time, incremental, or force-full outcomes. - Concrete Commands: Supplies the exact ingest and restart commands for each change type, covering both the Python and .NET RAG pipelines backed by Qdrant collections. - Pitfall Warnings: Documents common mistakes such as skipping --force-full after metadata-rules.yaml edits or forgetting to mirror glossary changes to the .NET copy. - Use Case: Before editing chunker.max_tokens in rag-config.yaml, consult the matrix to learn a full rebuild is required, then run python tools/rag/ingest.py --force-full and verify with compare_queries.py. ## Quick Start Ask the assistant to check whether your planned change to a RAG configuration file requires re-indexing before you edit it.