sync-docs

Reconcile documentation, code, and project knowledge to identify drift and gaps.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/aditya30103/ContentDeck --skill sync-docs-aditya30103
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-docs
Source: https://github.com/aditya30103/ContentDeck/tree/main/.claude/skills/sync-docs
Command: npx skills add https://github.com/aditya30103/ContentDeck --skill sync-docs-aditya30103

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically detects and corrects inconsistencies, gaps, and drift between your code, documentation, and project knowledge base, ensuring everything stays aligned and accurate.

Core Features & Use Cases

  • Comprehensive Auditing: Compares code, documentation (plans, logs, guides), skills, and memory to find discrepancies.
  • Automated Verification: Checks for factual alignment, correct pipeline steps, consistent branching conventions, and complete documentation cascades.
  • Use Case: After a development sprint, run /sync-docs to verify that all shipped features have corresponding log entries, the README.md accurately reflects the current architecture, and all skills use the correct co-authoring model.

Quick Start

Run the sync-docs skill to perform a full reconciliation across all project documentation and code.

Frequently Asked Questions about sync-docs

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

FAQPage Schema
How do I check for documentation drift between my code and project knowledge base?

To check for documentation drift, you reconcile code, documentation, and project memory to identify factual inconsistencies, pipeline gaps, and branching convention mismatches across multiple project layers.

What is the best way to ensure documentation matches reality after a development sprint?

The best way to ensure documentation matches reality is running a comprehensive reconciliation audit that validates factual alignment, pipeline integrity, and documentation cascades across code, skills, and memory.

How do I run a consistency check across project documentation and code layers?

You run a consistency check by executing a phased reconciliation process: Inventory, Code Grounding, Cross-Document Consistency, Completeness Check, and Remediation to identify and fix drift.

Can I use this documentation reconciliation process to audit GitHub issues and memory?

Yes, you can audit GitHub issues and memory because the reconciliation validates documentation cascades across multiple project layers including code, skills, memory, and GitHub issues.

What limitations exist when performing automated project knowledge base verification?

Limitations involve relying on existing project artifacts; the verification validates alignment and completeness across code, documentation, skills, and memory but requires these components to be present to detect drift.