# Doc Sync

> Detect stale documentation by comparing code, CLI surface area, and docs for drift.

- Skill: `eddieran/doc-sync` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add eddieran/doc-sync`
- Raw SKILL.md: https://api.skillmd.com/api/skills/eddieran/doc-sync/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: eddieran (https://skillmd.com/u/eddieran)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/eddieran/doc-sync

---


# Doc Sync

Use this skill when code changes may have made READMEs, CLI docs, API docs, or examples stale.

## Agent Compatibility

- Claude Code: supported
- Codex: supported

## Inputs

- The changed code or commit range
- The documentation surface that claims to describe that code
- Release notes, CLI help output, or API schemas when available

## Workflow

1. Enumerate the behavior that changed in code.
2. Find the documentation pages that claim to describe that behavior.
3. Compare signatures, commands, flags, examples, and defaults.
4. Report stale docs before proposing rewrites.
5. Prefer minimal, accurate doc updates over broad rewording.

## Output Contract

- Stale documentation findings first
- Exact files that drifted
- The implementation fact that now differs
- The smallest accurate doc update

## Guardrails

- Do not rewrite docs that are already correct.
- Do not invent undocumented features.
- Distinguish between wording polish and factual drift.