Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.
View on GitHubFebruary 5, 2026
Select agents to install to:
npx add-skill https://github.com/avifenesh/awesome-slash/blob/main/plugins/sync-docs/skills/sync-docs/SKILL.md -a claude-code --skill sync-docsInstallation paths:
.claude/skills/sync-docs/# sync-docs
Unified skill for syncing documentation with code state. Combines discovery, analysis, and CHANGELOG update into a single workflow.
## Quick Start - Agent Instructions
**Step 1**: Get changed files (use Bash):
```bash
# Recent changes (default scope)
git diff --name-only origin/main..HEAD 2>/dev/null || git diff --name-only HEAD~5..HEAD
# Or for all files
git ls-files '*.md'
```
**Step 2**: Find docs that reference changed files (use Grep):
- Search for filenames, function names, class names in `*.md` files
- Check README.md, CHANGELOG.md, docs/*.md
**Step 3**: Analyze each doc for issues:
- Version mismatches (compare doc versions to package.json)
- Removed exports (symbols in docs but not in code)
- Outdated code examples
- Import path changes
**Step 4**: Check CHANGELOG:
- Look for `## [Unreleased]` section
- Compare recent commit messages to CHANGELOG entries
**Step 5**: If repo-map exists (`{stateDir}/repo-map.json` - platform state directory):
- Load it to get accurate export list
- Find exports not mentioned in any documentation
- Report as `undocumented-export` issues
## Input
Arguments: `[report|apply] [--scope=all|recent|before-pr] [--include-undocumented]`
- **Mode**: `report` (default) or `apply`
- **Scope**:
- `recent` (default): Files changed since last commit to main
- `all`: Scan all docs against all code
- `before-pr`: Files in current branch, optimized for /next-task Phase 11
- **--include-undocumented**: Find exports not mentioned in any docs (uses repo-map)
## Architecture
This skill orchestrates all documentation sync operations:
```
sync-docs skill
|-- Phase 1: Detect project context
|-- Phase 2: Find related docs (lib/collectors/docs-patterns)
|-- Phase 3: Analyze issues
|-- Phase 3.5: Find undocumented exports (repo-map integration)
|-- Phase 4: Check CHANGELOG
|-- Phase 5: Return structured results
```
The skill MUST NOT apply fixes directly. It returns structured data for the orchestr