vault-sync

Detect and repair drift between an OKF knowledge vault and source code.

395|84|Updated Oct 5, 2025

Search Tags:#automation #documentation #sync #drift-detection #code-integrity #knowledge-vault

Ready to run

npx skills add https://github.com/bybren-llc/safe-agentic-workflow --skill vault-sync-bybren-llc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vault-sync
Source: https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.gemini/skills/vault-sync
Command: npx skills add https://github.com/bybren-llc/safe-agentic-workflow --skill vault-sync-bybren-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves the common issue of documentation drift, where a knowledge base becomes disconnected from the actual state of the codebase, leading to unreliable and stale information.

Core Features & Use Cases

Drift Detection: Automatically identifies discrepancies between source code and documented concepts by comparing baseline SHAs against current HEAD.
Targeted Regeneration: Updates only the specific concepts affected by code changes, ensuring the vault remains accurate without unnecessary overhead.
Validation Gate: Enforces strict validation rules to ensure the vault remains a trustworthy source of truth for the team.

Quick Start

Invoke the vault sync skill to detect and repair any drift between the current codebase and the knowledge vault.

Frequently Asked Questions about vault-sync

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

FAQPage Schema

How do I detect documentation drift between my source code and knowledge vault?▼

Documentation drift is detected by comparing baseline SHAs against the current HEAD to identify discrepancies between source code and documented concepts. This automated process flags stale concepts that have diverged from verified source changes.

How do I update stale knowledge vault concepts after code changes?▼

To update stale knowledge vault concepts, targeted regeneration applies verified source changes only to the specific affected concepts. This ensures the vault remains accurate without unnecessary overhead from regenerating unaffected documentation.

What is an OKF knowledge vault and when do I need to sync it?▼

An OKF knowledge vault is a documented concept base that requires syncing when it becomes disconnected from the actual codebase state. You need to sync it to maintain documentation accuracy and prevent unreliable, stale information.

Do I need manifest-based ID registries to maintain code documentation accuracy?▼

Yes, manifest-based ID registries are required to maintain code documentation accuracy. Strict adherence to these registries, combined with automated validation scripts, enforces the rules ensuring the vault remains a trustworthy source of truth.

What's the best way to validate a knowledge vault against source code changes?▼

The best way to validate a knowledge vault against source code changes is enforcing a validation gate with automated scripts. This gate checks manifest-based ID registries to ensure the vault remains a trustworthy source of truth for the team.

Why does my documentation show stale concepts after updating the codebase?▼

Stale concepts appear because documentation drift occurs when baseline SHAs do not match the current HEAD. Without targeted regeneration based on verified source changes, the knowledge base remains disconnected from the actual codebase state.