document-sync

# Document Sync Skill for Claude Code

## Overview

This skill provides comprehensive documentation synchronization by analyzing your actual codebase, tech stack, configuration, and architecture to ensure all documentation remains current and accurate. It operates on a "verify, never assume" principle, performing end-to-end comparisons against real code and dependencies to detect documentation drift automatically.

## Core Principles

- **Verify, Never Assume:** Documentation is only updated after end-to-end comparison against real, current code and dependencies
- **Deep System Introspection:** Checks languages, frameworks, APIs, DBs, config, code patterns, and deployment targets
- **Doc Trust Score:** Every doc gets a trust rating based on evidence found in the codebase and config files

## Quick Start

**Natural Language Commands:**
- "Run document sync analysis on my project"
- "Update docs so every API route matches the code"
- "Check if any doc mentions features no longer in the app"
- "List undocumented config variables"

**Slash Commands:**
- `/docs-sync` — Runs analysis and outputs a complete report on outdated/inaccurate sections
- `/docs-update-strict` — Suggests only changes verified by found code/config evidence
- `/docs-rewrite-missing` — Fills gaps for undocumented features based on live source
- `/docs-patch-pr` — Makes all doc changes as a PR, zero surprises

## Operation Workflow

### Phase 1: Full System Scan

Execute the system scanning script to analyze your codebase:

```bash
# Run comprehensive system scan
python3 .claude/skills/document-sync/scripts/system_scan.py
```

This phase automatically:
1. **Tech Stack Detection** - Parse `package.json`, `requirements.txt`, `pom.xml`, etc. for frameworks, DBs, and build tools
2. **Project Structure Analysis** - Map `src/`, `lib/`, `app/`, and `config/` directories for real usage
3. **Architecture Detection** - Identify data flows, auth methods, sync strategies, and cloud/on-prem deployment

**Key Outpu