Does it support monorepos?

Yes, it is explicitly designed with monorepo structure awareness, specifically for the PopKit plugin ecosystem.

How does it identify where to update the documentation?

It uses specific HTML comment markers like and END within the markdown files to locate updateable sections.

What is the primary purpose of pop-doc-sync?

It synchronizes auto-generated sections of documentation by reading source-of-truth configuration files like plugin.json and config.json.

Can I use this to write new documentation prose?

No, this skill is specifically for syncing versions and counts; it is not intended for writing or generating new descriptive text.

Which files does it check for the source of truth?

It reads plugin.json, marketplace.json, config.json, and hooks.json, and scans directory structures for skills, commands, and utility modules.

Documentation Sync

Name: Documentation Sync
Author: jrc1883

byjrc1883

Content Management

Synchronizes documentation markers by reading source-of-truth files to ensure agent counts, versions, and repository structures remain accurate.

About

The pop-doc-sync skill automates the maintenance of project documentation by extracting real-time data from source files like plugin.json and config.json to update markers in CLAUDE.md. It is specifically designed for PopKit monorepos to prevent documentation drift in technical counts—such as agents, skills, and hooks—and to ensure versioning consistency across plugin and marketplace files. This tool is essential for developers who need to keep high-level documentation perfectly aligned with their evolving codebase without manual counting or tedious editing.

Key Features

Support for Fix Mode to automatically apply corrections using Claude's edit tools
Marker-based updates using AUTO-GEN sections in CLAUDE.md
Monorepo-aware scanning for agents, skills, commands, and hooks
Version synchronization across plugin.json, marketplace.json, and CHANGELOG.md
Automated drift detection between source files and documentation
0 GitHub stars

Use Cases

Auditing documentation accuracy during routine health checks or CI processes
Ensuring version numbers match across all metadata files before a release
Updating documentation after adding new agent skills or slash commands

About

Key Features

Support for Fix Mode to automatically apply corrections using Claude's edit tools
Marker-based updates using AUTO-GEN sections in CLAUDE.md
Monorepo-aware scanning for agents, skills, commands, and hooks
Version synchronization across plugin.json, marketplace.json, and CHANGELOG.md
Automated drift detection between source files and documentation
0 GitHub stars

Use Cases

Auditing documentation accuracy during routine health checks or CI processes
Ensuring version numbers match across all metadata files before a release
Updating documentation after adding new agent skills or slash commands