reindex-all-vectors

Reindex all configured vector databases for fresh semantic code search.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dmzoneill/skills --skill reindex-all-vectors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reindex-all-vectors
Source: https://github.com/dmzoneill/skills/tree/main/reindex-all-vectors
Command: npx skills add https://github.com/dmzoneill/skills --skill reindex-all-vectors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your semantic code search remains up-to-date by reindexing all configured vector databases, preventing outdated search results.

Core Features & Use Cases

  • Comprehensive Reindexing: Updates vector indexes for all projects or a specified subset.
  • Freshness Maintenance: Keeps semantic code search accurate and relevant.
  • Use Case: When you've made significant code changes across multiple projects and want to ensure your AI assistant can find the most relevant code snippets, run this skill.

Quick Start

Run the reindex-all-vectors skill to refresh all vector databases.

Frequently Asked Questions about reindex-all-vectors

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

FAQPage Schema
How do I refresh all vector databases for semantic code search?

To refresh vector databases for semantic code search, run this skill to iterate through configured repositories and update vector indexes, ensuring search results remain accurate and up-to-date across all projects.

When do I need to reindex vectors for my code repositories?

You need to reindex vectors when you've made significant code changes across multiple projects and want to ensure your AI assistant can find the most relevant code snippets during semantic search.

Can I force a full re-indexing of all configured vector databases?

Yes, you can force a full re-indexing of all configured vector databases by using the supported force flag, which overrides incremental updates and rebuilds the entire index for your projects.

Does reindexing vector databases restart file watchers automatically?

Reindexing vector databases optionally restarts watchers after iterating through repositories and running code indexing per project, allowing you to maintain continuous semantic search monitoring.

What's the best way to update semantic search indexes across multiple projects?

The best way to update semantic search indexes across multiple projects is to run a comprehensive reindexing skill that iterates through all configured repositories and refreshes vector databases to prevent outdated search results.