sync

Synchronize vault documents with codebase changes while preserving designer annotations.

Updated Mar 26, 2026

Search Tags:#codebase #diff #vault #sync #annotations #knowledge-base

Ready to run

npx skills add https://github.com/Valyay/vibe-design-kit --skill sync-valyay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/Valyay/vibe-design-kit/tree/main/skills/sync
Command: npx skills add https://github.com/Valyay/vibe-design-kit --skill sync-valyay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize the knowledge base with the current codebase to ensure vault documents reflect the latest changes and preserve designer annotations.

Core Features & Use Cases

Detect changes across the codebase and vault, categorize as new, modified, or deleted.
Update stale vault documents while preserving designer annotations.
Flag conflicts when designer notes disagree with generated data.
Apply at start of work sessions or after major changes to keep the vault healthy.

Quick Start

Run the sync skill at the start of a work session to refresh the vault from the latest code changes.

Frequently Asked Questions about sync

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

FAQPage Schema

How do I synchronize my knowledge base with my current codebase?▼

To synchronize your knowledge base with your codebase, run the sync skill at the start of a work session. It detects new, modified, or deleted items by comparing last_synced dates and updates vault documents to reflect the latest code changes.

How do I preserve designer annotations when updating vault documents?▼

Preserving designer annotations during vault updates is handled automatically by the sync process. It reconciles generated content with the latest codebase while specifically protecting existing designer notes and flagging any conflicts between notes and generated data.

When should I run a vault sync against my codebase?▼

You should run a vault sync at the start of a work session or immediately after major code changes. This ensures your knowledge base documents remain accurate and reflect the latest state of your codebase without accumulating stale information.

What happens when designer notes disagree with generated vault data?▼

When designer notes disagree with generated vault data, the sync process flags these items as conflicts. It identifies discrepancies during the codebase comparison and highlights them so you can manually review the mismatched annotations before updating.

How are deleted codebase items handled during knowledge base synchronization?▼

Deleted codebase items are detected and categorized during knowledge base synchronization. The sync skill compares per-document last_synced dates across the vault and codebase to identify missing items, ensuring your vault documents accurately reflect removals.

Can I detect codebase changes in my vault without overwriting manual notes?▼

Yes, you can detect codebase changes without overwriting manual notes. The sync skill categorizes new, modified, and deleted items, then updates generated vault content while explicitly preserving your designer annotations and flagging any detected conflicts.