sync

Sync the codebase context map in the `.vibe/` directory.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/neolao/claude-plugin-vibe --skill sync-neolao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/neolao/claude-plugin-vibe/tree/main/skills/sync
Command: npx skills add https://github.com/neolao/claude-plugin-vibe --skill sync-neolao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the synchronization of the .vibe/ directory, ensuring Claude has an up-to-date understanding of the codebase for efficient coding sessions.

Core Features & Use Cases

  • Automated Sync: Generates or updates the codebase context map automatically.
  • Incremental Updates: Only updates modules whose source files have changed since the last sync.
  • Full Regeneration: Forces full regeneration with the --full argument.
  • Use Case: Use /vibe:sync to ensure Claude has the latest context when beginning a coding session, or use /vibe:sync --full to regenerate the entire context map.

Quick Start

Run /vibe:sync to sync the codebase context map for a new session.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I sync a codebase context map for Claude sessions?

Running an automated sync updates the structured context map in the `.vibe/` directory, ensuring Claude has an up-to-date understanding of the codebase for efficient coding sessions.

What is incremental codebase context map update?

Incremental context map update only refreshes modules whose source files have changed since the last sync, interpreting commit history and file status to execute targeted updates efficiently.

How do I force full regeneration of a codebase context map?

Force full regeneration of the codebase context map by running the sync command with the `--full` argument, which rebuilds the entire structured context map in the `.vibe/` directory.

Do I need source directory access to sync codebase context maps?

Yes, syncing codebase context maps requires access to source directories and the ability to interpret commit history and status to accurately detect file changes for incremental updates.

When should I use a full context map regeneration instead of incremental sync?

Use full context map regeneration instead of incremental sync when you need to completely rebuild the `.vibe/` directory structure, bypassing the changed-file detection mechanism used for incremental updates.