Can I use Doc Sync to update my README after a commit?

Absolutely. In Mode B, the skill analyzes your recent code changes (git diff) and automatically identifies which documentation sections need updates to match the new API.

What is the 'Ground Truth' hierarchy used by this skill?

The skill prioritizes working implementations in the codebase as the highest truth, followed by the formal API definition, treating existing documentation as the least reliable source until verified.

How does Doc Sync verify if a code example is correct?

It extracts function signatures and parameters from documentation files and compares them against the current live API and verified working implementations in the codebase.

Does this skill work with both additions and deletions?

Yes. It specifically focuses on deletions and breaking changes in Git history, as these are the most common causes of documentation rot and broken examples.

Doc Sync

Name: Doc Sync
Author: Microck

byMicrock

•

Learning & Documentation

Synchronizes project documentation with real-world code implementations and API changes to ensure accuracy.

About

Doc Sync is a specialized Claude Code skill designed to eliminate outdated documentation by treating it as 'guilty until proven innocent' after any code changes. It proactively verifies function signatures, parameter names, and usage patterns in Markdown files against the actual codebase and Git history to ensure technical accuracy. By establishing a 'ground truth' from working implementations and analyzing recent breaking changes, the skill helps developers maintain reliable READMEs, contribution guides, and API documentation without manual auditing overhead.

Key Features

Bidirectional verification between code changes and documentation files
Ground truth pattern matching using real-world implementations from the codebase
Automated extraction and validation of code snippets and function signatures in Markdown
81 GitHub stars
Detailed discrepancy reporting with severity levels and recommended fixes
Git history analysis to identify deleted or deprecated API elements that break docs

Use Cases

Updating project READMEs and API guides immediately after a breaking refactor
Auditing existing documentation folders to find and fix broken code examples
Verifying that new contributions include accurate updates to documentation and examples

About

Key Features

Bidirectional verification between code changes and documentation files
Ground truth pattern matching using real-world implementations from the codebase
Automated extraction and validation of code snippets and function signatures in Markdown
81 GitHub stars
Detailed discrepancy reporting with severity levels and recommended fixes
Git history analysis to identify deleted or deprecated API elements that break docs

Use Cases

Updating project READMEs and API guides immediately after a breaking refactor
Auditing existing documentation folders to find and fix broken code examples
Verifying that new contributions include accurate updates to documentation and examples