sync-index

Synchronize project index and agent guidance files with the current codebase structure.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/B4san/Calix-Pass --skill sync-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-index
Source: https://github.com/B4san/Calix-Pass/tree/main/.gemini/skills/sync-index
Command: npx skills add https://github.com/B4san/Calix-Pass --skill sync-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common issue of documentation becoming outdated and inaccurate as the codebase evolves, ensuring project documentation remains a reliable source of truth.

Core Features & Use Cases

  • Automated Documentation Updates: Automatically synchronizes project index files (.agents/project-index.md) and agent guidance with the current state of the codebase.
  • Drift Detection: Compares file structure against existing documentation to identify discrepancies.
  • Use Case: After adding a new module or refactoring existing code, run this Skill to ensure that project-index.md and relevant agent guides are updated to reflect these changes, preventing outdated information.

Quick Start

Run the sync-index skill to update project documentation based on recent code changes.

Frequently Asked Questions about sync-index

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

FAQPage Schema
How do I keep project documentation in sync with codebase changes?

To keep project documentation in sync, you can automate the process by detecting structural codebase changes, running an indexer, and updating guidance files to prevent documentation drift.

What is documentation drift and how do I fix it?

Documentation drift happens when project docs become outdated as code evolves. You fix it by detecting discrepancies between the file structure and existing docs, then updating the project index automatically.

How do I update agent guidance files after refactoring code?

You update agent guidance files by synchronizing them with the current codebase structure, ensuring that files like project-index.md accurately reflect your recent refactoring changes.

Does automated documentation sync work for large codebases?

Automated documentation sync works for large codebases by comparing the entire file structure against existing documentation to identify and update discrepancies without manual intervention.

Why are my agent guidance files inaccurate after adding a new module?

Agent guidance files become inaccurate after adding a module because documentation drift occurs. Running an indexer detects these codebase changes and updates the guidance files accordingly.