doc-sync

Synchronize repository documentation across CLAUDE.md and README.md indexes.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/marqus0004/LifeIsRoadBlocks --skill doc-sync-marqus0004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-sync
Source: https://github.com/marqus0004/LifeIsRoadBlocks/tree/main/skills/doc-sync
Command: npx skills add https://github.com/marqus0004/LifeIsRoadBlocks --skill doc-sync-marqus0004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It synchronizes repository documentation to maintain a consistent CLAUDE.md/README.md index and invisible knowledge.

Core Features & Use Cases

  • Maintains CLAUDE.md navigation hierarchy and README.md invisible knowledge docs across a repository.
  • Executes a five-phase workflow: discovery, audit, migration, update, and verification to ensure documentation drift is eliminated.
  • Supports targeted scope resolution to audit and migrate documentation within specific directories when needed.

Quick Start

Run the doc-sync skill to audit and align CLAUDE.md and README.md across the repository.

Frequently Asked Questions about doc-sync

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

FAQPage Schema
How do I keep CLAUDE.md and README.md documentation indexes in sync across a repository?

Documentation synchronization aligns CLAUDE.md and README.md indexes by running a five-phase workflow—discovery, audit, migration, update, and verification—to eliminate drift and consolidate invisible knowledge across the repository.

What is the best way to audit repository documentation structure and fix drift?

The best way to audit documentation drift is applying a five-phase synchronization workflow that discovers files, audits index alignment, migrates content, updates references, and verifies the final structure for consistent repository governance.

Can I scope documentation migration to specific directories instead of the whole repository?

Yes, documentation migration supports targeted scope resolution, allowing you to audit, migrate, and verify the documentation structure within specific directories instead of running a full repository-wide update.

How does the discovery and audit phase work for repository documentation?

The discovery and audit phase scans the repository to locate CLAUDE.md and README.md files, indexes their navigation hierarchies, and identifies invisible knowledge or structural drift before proceeding to migration and update phases.

When do I need to run a documentation synchronization workflow for my project?

You need to run a documentation synchronization workflow when your CLAUDE.md navigation hierarchy and README.md invisible knowledge docs accumulate drift, requiring a structured audit, migration, and verification process to restore consistent repository governance.