document-hub-analyze

Detect drift between codebase documentation and actual code with Python scripts.

3|Updated Nov 20, 2025

Search Tags:#documentation #codebase #glossary #reporting #drift-detection #analyze #structure-validation

Ready to run

npx skills add https://github.com/artsmc/claude-dev-agents --skill document-hub-analyze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-hub-analyze
Source: https://github.com/artsmc/claude-dev-agents/tree/main/skills/document-hub-analyze
Command: npx skills add https://github.com/artsmc/claude-dev-agents --skill document-hub-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill analyzes documentation quality and detects drift between the codebase and its documentation, surfaces undocumented code, and identifies glossary gaps to inform actionable improvements without making changes.

Core Features & Use Cases

Drift detection between source code and documentation using scripts/detect_drift.py
Glossary gap extraction using scripts/extract_glossary.py
Structure validation using scripts/validate_hub.py
Useful for periodic documentation audits, pre-update planning, and governance reporting.

Quick Start

Run validation, drift, and glossary checks to produce a report:

python scripts/validate_hub.py /path/to/project
python scripts/detect_drift.py /path/to/project
python scripts/extract_glossary.py /path/to/project

Frequently Asked Questions about document-hub-analyze

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

FAQPage Schema

How do I detect drift between my codebase and Markdown documentation?▼

Documentation drift detection compares source code against Markdown files to surface undocumented modules and glossary gaps. Running scripts like detect_drift.py and extract_glossary.py generates reports showing where code and documentation no longer align.

What is documentation drift detection and when do I need it?▼

Documentation drift detection identifies discrepancies between a codebase and its Markdown documentation to surface undocumented modules and glossary gaps. You need it for periodic documentation audits, pre-update health checks, and governance planning.

How do I audit codebase documentation for glossary gaps and undocumented modules?▼

Run glossary gap extraction and structure validation scripts against your project path to audit Markdown documentation. This surfaces undocumented modules and missing glossary terms, producing reports that inform actionable documentation improvements.

Does documentation drift detection require a specific project architecture or Python setup?▼

Documentation drift detection requires Python 3 and a project using a modular hub architecture with Markdown documentation. You run the validation, drift, and glossary extraction scripts against your project path to generate analysis results.

Can I validate modular hub architecture structure before updating documentation?▼

Yes, you can validate modular hub architecture structure before updating documentation by running validate_hub.py against your project path. This produces a structural validation report to guide pre-update planning and governance reporting.

What is the best way to automate documentation audits for codebase governance reporting?▼

The best way to automate documentation audits for governance reporting is running Python scripts for drift detection, glossary extraction, and structure validation. This generates reports on undocumented code and glossary gaps without making changes.