vault-reindex

Rebuild SQLite FTS5 vault indexes incrementally or with --full.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/abhattacherjee/obsidian-brain --skill vault-reindex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-reindex
Source: https://github.com/abhattacherjee/obsidian-brain/tree/main/skills/vault-reindex
Command: npx skills add https://github.com/abhattacherjee/obsidian-brain --skill vault-reindex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rebuild the SQLite FTS5 vault index non-destructively to refresh the note searchability while preserving activation data (access_log, themes, theme_members); only regenerates derivable tables.

Core Features & Use Cases

  • Incremental indexing: Reconciles on-disk vault state with the index, indexing newly added notes and removing deleted ones without touching preserved activation history.
  • Destructive full rebuild option: Use --full to delete and recreate the entire database when schema issues arise.
  • Safe operation guidance: Preserves access_log, themes, and theme_members by default; prompts for confirmation in destructive mode.

Quick Start

Run the /vault-reindex command to rebuild the vault index.

Frequently Asked Questions about vault-reindex

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

FAQPage Schema
How do I rebuild a stale SQLite FTS5 vault index without losing activation data?

To rebuild a stale SQLite FTS5 vault index safely, run an incremental reindex that reconciles on-disk note changes while preserving access log, themes, and theme member tables. This refreshes searchability without destroying historical activation data.

When should I use a destructive full rebuild on my vault database?

Use a destructive full rebuild when database schema issues arise and incremental indexing fails. Invoking the rebuild with the --full flag wipes and recreates the entire database, requiring confirmation before proceeding to prevent unintended data loss.

Does incremental indexing support newly added and deleted notes in Obsidian vaults?

Yes, incremental indexing supports Obsidian vaults by detecting newly added notes for indexing and removing deleted ones from the database. It reconciles the on-disk vault state with the index while leaving preserved activation history untouched.

What is the best way to refresh note searchability after bulk edits to a vault?

The best way to refresh note searchability after bulk edits is running a delta index command. It reads vault configuration and updates the SQLite FTS5 index with only the changed files, keeping preserved tables intact and avoiding a full database wipe.

Why does the vault reindex process preserve access logs and theme tables?

The vault reindex process preserves access logs and theme tables because these contain non-derivable activation history. Reindexing only regenerates derivable tables to ensure historical data remains safe during standard delta updates or full rebuilds.

Can I use vault-reindex with Claude Code to automate SQLite database refreshes?

Yes, vault-reindex enforces a CLI workflow implemented in Bash and Python compatible with Claude Code. It reads vault configuration and runs delta or full database refreshes directly from the command line to automate searchability updates.