Overview

Matrix Reindex triggers a manual refresh of the TypeScript/JavaScript code index. Use it after significant file changes, to fix a stale or incomplete index, or after renaming or moving many files to ensure symbols and imports are up to date.

How This Skill Works

It uses the matrix_reindex MCP tool to re-scan and rebuild the code index. You can pass an optional full flag to force a complete reindex, ignoring incremental mode. The tool returns what was scanned, what was indexed, what was skipped, the symbols found, imports discovered, and the total duration.

When to Use It

• After significant file changes outside of Claude
• When the index seems stale or incomplete
• After renaming or moving many files
• After dependency updates or codebase restructuring
• When you need to ensure symbol resolution reflects the latest code

Quick Start

1. Step 1: Invoke the Matrix Reindex skill
2. Step 2: Run matrix_reindex with full=true to force a complete reindex if needed
3. Step 3: Review the output: files scanned, indexed, skipped; symbols, imports, duration

Best Practices

• Run reindex after large refactors or bulk moves
• Prefer incremental reindexes for small changes; reserve full when necessary
• Verify the output lists symbols and imports and note the duration
• Avoid triggering reindex during critical CI tasks
• Document the reindex outcome for future reference

Example Use Cases

• Reindex after a bulk file rename across the project
• Refresh the index when Claude reports missing symbols
• Force a full reindex after a major dependency or codebase restructure
• Update symbol index after moving folders containing modules
• Manual reindex when new code isn't appearing in search results

Frequently Asked Questions