Skip to content
Back to skills

Docs Sync

ASecurity

Sync user documentation with design doc changes. Use when design docs

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 8, 2026
documentationbashapidocumentation

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill docs-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Docs Sync?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Docs Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-docs-sync/badge)](https://www.skillsdirectory.com/skills/majiayu000-docs-sync)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: docs-sync
description: Sync user documentation with design doc changes. Use when design docs
  have been updated and user docs need to reflect the changes.
allowed-tools: Read, Glob, Edit, Write
context: fork
agent: docs-gen-agent
---

# Sync User Documentation

Syncs user documentation with changes in design docs to keep them current.

## Overview

This skill detects changes in design docs and updates corresponding
user documentation by:

1. Comparing design doc timestamps with user doc timestamps
2. Identifying which user docs are affected
3. Regenerating or updating affected sections
4. Preserving custom user-added content
5. Updating sync timestamps

## Quick Start

**Sync all levels for a module:**

```bash
/docs-sync effect-type-registry
```

**Sync specific level only:**

```bash
/docs-sync rspress-plugin-api-extractor --level=1
```

**Preview changes without writing:**

```bash
/docs-sync website --dry-run
```

## How It Works

### 1. Parse Parameters

- `module`: Module to sync [REQUIRED]
- `--level`: Sync specific level (1=README, 2=repo, 3=site)
- `--dry-run`: Preview changes without writing

### 2. Detect Changes

Compare timestamps:

- Design doc `updated` field
- User doc last modification time
- Identify stale user docs (design newer than user docs)

### 3. Analyze Impact

For each changed design doc:

- Determine which user docs it affects
- Identify sections that need updates
- Check for breaking changes

### 4. Update User Documentation

Update strategies:

- **README** - Regenerate features, quick start, API overview
- **Repository Docs** - Update affected topic guides
- **Site Docs** - Refresh concept docs and guides

### 5. Preserve Custom Content

Protect user additions:

- Custom examples
- Additional sections
- Badges and shields
- Screenshots and GIFs

### 6. Update Timestamps

Mark synced docs with current timestamp.

## Supporting Documentation

- `instructions.md` - Detailed sync process
- `examples.md` - Sync scenarios and outputs

## Success Criteria

- ✅ Stale docs identified correctly
- ✅ Affected sections updated
- ✅ Custom content preserved
- ✅ Timestamps updated
- ✅ No broken links introduced

## Integration Points

- Uses `.claude/design/design.config.json`
- Reads design docs from `designDocsPath`
- Updates files in `userDocs` paths
- Respects quality standards

## Related Skills

- `/docs-generate-readme` - Regenerate README
- `/docs-generate-repo` - Regenerate repo docs
- `/docs-generate-site` - Regenerate site docs
- `/docs-review` - Review sync quality

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.