partial-reindex

Re-index changed regions within the File Navigation harness.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill partial-reindex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: partial-reindex
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/partial-reindex
Command: npx skills add https://github.com/AesopScott/mojo --skill partial-reindex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the high cost and inefficiency of full-system reindexing by enabling targeted, partial updates to the file navigation graph.

Core Features & Use Cases

  • Cost Efficiency Control: Limits token usage, compute cycles, and storage overhead by re-indexing only modified regions.
  • Harness Maintenance: Provides a structured runbook for modifying File Navigation boundaries, ownership paths, and capability-to-code links.
  • Use Case: When updating a specific configuration or prompt within the File Navigation harness, use this skill to apply changes to the affected graph segment rather than triggering a full-rebuild of the entire system.

Quick Start

Execute the partial-reindex command to update the File Navigation harness after modifying the specific configuration boundary.

Frequently Asked Questions about partial-reindex

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

FAQPage Schema
How do I reduce compute costs when updating file navigation graphs?

Reduce compute costs by performing targeted, partial re-indexing of modified graph regions rather than full-system rebuilds. This limits token usage, compute cycles, and storage overhead during file navigation harness maintenance.

What is partial re-indexing for file navigation harness maintenance?

Partial re-indexing is applying bounded change management to update specific configuration boundaries, ownership paths, and capability-to-code links. It enables safe verification of configuration updates while maintaining cost-efficiency.

When do I need to use partial graph updates instead of a full reindex?

Use partial graph updates when modifying specific configurations or prompts within the file navigation harness. This approach minimizes computational and token expenditure by re-indexing only changed regions.

How to apply bounded change management to file navigation boundaries?

Apply bounded change management by executing targeted re-indexing after modifying a configuration boundary. This structured runbook updates affected graph segments while providing observability and safe verification of updates.

What's the best way to maintain cost-efficiency during graph updates?

Maintain cost-efficiency by triggering targeted re-indexing of only the modified regions within the file navigation harness. This avoids expensive full-system reindexing and limits token usage and storage overhead.