Can I run the scan on a specific folder only?

Yes, you can provide a subtree path as an argument to limit the scan to a specific directory, such as 'src/api' or 'lib/core'.

What happens if I don't have a manifest file?

The skill requires a .mcp/manifest.yml file to function. If one isn't found, it will prompt you to run the initialization command first.

How are documentation priorities calculated?

Priorities are determined by directory importance; entry points and core API routes are marked as Critical, while utility and shared logic folders are High, and test or tool folders are Low.

How does the scan determine what needs documentation?

The skill identifies 'significant' directories—those containing source code files or module boundary configurations like package.json, go.mod, or Cargo.toml—and checks if they have associated documentation.

MCP Documentation Coverage Scanner

Name: MCP Documentation Coverage Scanner
Author: Z-M-Huang

byZ-M-Huang

•

Content Management

Analyzes project directories to identify undocumented source code and stale manifest entries with prioritized improvement recommendations.

The mcp-doc-scan skill provides a comprehensive audit of your project's documentation health by comparing your actual file system against the Vibe Coding Protocol manifest. It intelligently identifies significant directories containing source code or module boundaries, categorizes their documentation status, and generates a prioritized roadmap for filling gaps. By highlighting stale entries and undocumented critical modules, it ensures your project remains navigable for both human developers and AI agents.

Key Features

01Heuristic-based prioritization engine for documentation recommendations

02Automated discovery of undocumented source code and module directories

03Comprehensive coverage reporting including non-markdown documentation assets

04Manifest synchronization check to identify stale or missing index entries

058 GitHub stars

06Scoped subtree scanning for targeted documentation audits

Use Cases

01Maintaining documentation manifest integrity after large-scale refactoring

02Auditing legacy codebases to identify and prioritize missing documentation

03Ensuring codebase readiness for AI-assisted development and onboarding

Key Features

01Heuristic-based prioritization engine for documentation recommendations

02Automated discovery of undocumented source code and module directories

03Comprehensive coverage reporting including non-markdown documentation assets

04Manifest synchronization check to identify stale or missing index entries

058 GitHub stars

06Scoped subtree scanning for targeted documentation audits

Use Cases

01Maintaining documentation manifest integrity after large-scale refactoring

02Auditing legacy codebases to identify and prioritize missing documentation

03Ensuring codebase readiness for AI-assisted development and onboarding