skills.rest
jrc1883
jrc1883COMMUNITY
Explore all skills by this author →
GitHub

doc-sync

Synchronize documentation counts and versions in CLAUDE.md from source-of-truth files.

Updated Aug 23, 2026
Search Tags:#automation#documentation#monorepo#sync#CLAUDE.md
One-click install
npx skills add https://github.com/jrc1883/popkit-claude --skill doc-sync-jrc1883
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-sync
Source: https://github.com/jrc1883/popkit-claude/tree/main/skills/pop-doc-sync
Command: npx skills add https://github.com/jrc1883/popkit-claude --skill doc-sync-jrc1883

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates alignment of auto-generated documentation sections by reading source-of-truth files (plugin.json, config.json, hooks.json) and updating markers in CLAUDE.md. Do NOT use for writing new prose - this is specifically for keeping counts and versions in sync.

Core Features & Use Cases

  • Marker-based syncing: updates sections between <!-- AUTO-GEN:SECTION-NAME START/END --> markers to reflect real data.
  • Monorepo awareness: understands the repository structure and counts across packages.
  • Use Case: keep CLAUDE.md in sync after every release to prevent drift in counts and versions.

Quick Start

Run the doc-sync skill to refresh CLAUDE.md counts using the repository source-of-truth files.

Frequently Asked Questions about doc-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep documentation counts synchronized across a monorepo?▼

Documentation counts stay synchronized by reading source-of-truth files like plugin.json and config.json, then updating auto-generated sections in CLAUDE.md between designated markers. This prevents drift between actual counts and documented values across packages.

What files does doc-sync read to update CLAUDE.md?▼

doc-sync reads plugin.json, marketplace.json, config.json, hooks.json, and SKILL.md as sources of truth. It compares their actual counts and versions against markers in CLAUDE.md and updates mismatches in auto-generated sections.

Can doc-sync detect and fix documentation drift automatically?▼

Yes. doc-sync performs drift detection by comparing source files against current CLAUDE.md markers. An optional fix mode applies updates automatically, ensuring counts and versions reflect the actual repository state.

When should I run doc-sync in my release workflow?▼

Run doc-sync after every release to refresh CLAUDE.md counts and versions. This prevents documentation from drifting out of alignment with actual plugin, hook, and configuration counts in your monorepo.

Does doc-sync modify prose content or only auto-generated sections?▼

doc-sync updates only auto-generated sections marked with `<!-- AUTO-GEN:SECTION-NAME START/END -->` comments. It does not write new prose—use it strictly for keeping counts and versions in sync.

Related Skills

Explore More Software Engineering Skills→
vzcovzco
15

bump-version

Update and verify version numbers across plugin and marketplace config files.

Official
Intermediate
j0KZj0KZ

project-standardization

Synchronize package versions and enforce repository standards from version.json.

Community
Advanced
ayubunayubun
8

maintaining-a-marketplace

Maintain opencode Plugin Marketplace consistency across plugin.json, marketplace.json, and CHANGELOG.md.

Community
Intermediate
kanyun-inckanyun-inc
58

skill-sync-checker

Detect content drift between AI skill files and source documents via markers.

Official
Intermediate