docs-consolidator

Audit and consolidate project documentation into a centralized doc registry.

Updated Nov 6, 2023
One-click install
npx skills add https://github.com/cryptofish7/dotfiles --skill docs-consolidator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-consolidator
Source: https://github.com/cryptofish7/dotfiles/tree/main/config/claude/skills/docs-consolidator
Command: npx skills add https://github.com/cryptofish7/dotfiles --skill docs-consolidator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit, deduplicate, and reorganize project documentation so every piece of information has a single home and all docs stay current.

Core Features & Use Cases

  • Inventory and categorize docs across repositories (docs/, CLAUDE.md, README.md) to establish ownership and canonical locations.
  • Detect duplicates, outdated references, and misplaced content; propose canonical homes and cross-references.
  • Generate or update a documentation registry at .claude/skills/docs-consolidator/references/doc-registry.md to guide future maintenance.

Quick Start

Run the docs-consolidator skill to audit, deduplicate, and reorganize your project documentation, ensuring a single source of truth.

Frequently Asked Questions about docs-consolidator

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

FAQPage Schema
How do I consolidate duplicate documentation across a monorepo?

To consolidate duplicate documentation across a monorepo, you can inventory and categorize scattered files like docs/, CLAUDE.md, and README.md to detect duplication and establish a single canonical source for every piece of information.

What is a documentation registry and how does it help manage scattered docs?

A documentation registry is a centralized index that centralizes ownership and canonical sources for project docs. It helps manage scattered docs by guiding future maintenance and ensuring all information has a single home.

How do I audit project documentation to find stale references and misplaced content?

You audit project documentation by scanning existing files to detect duplicates, outdated references, and misplaced content. The audit then proposes canonical homes and cross-references to remediate the documentation.

Can I use this approach to reorganize documentation for multi-team projects?

Yes, you can use this approach to reorganize documentation for multi-team projects. It is specifically designed to inventory, categorize, and deduplicate scattered docs while assigning ownership domains across multiple teams.

What is the best way to maintain a single source of truth for project documentation?

The best way to maintain a single source of truth is to audit and deduplicate project docs, then generate a top-level documentation registry to centralize ownership and ensure every piece of information has a single home.