From ekline-docs-skills
Measure documentation coverage by scanning your codebase for exported functions, classes, API endpoints, and CLI commands, then checking if docs exist. Runs a helper script that reports coverage percentage, breakdowns by type and directory, and lists undocumented items. Supports TypeScript/JavaScript, Python, and Go.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ekline-docs-skills:docs-coverageThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the helper script to measure what percentage of your public API surface is documented.
Run the helper script to measure what percentage of your public API surface is documented.
$ARGUMENTS — optional source directory and optional --docs-dir DIR for the docs directorypython scripts/scan_exports.py $ARGUMENTS
Pass --docs-dir DIR if the user specifies a docs directory. Capture the JSON output.
The script handles:
Supports TypeScript/JavaScript, Python, and Go. Max 300 source files per run.
If the JSON contains an error field:
not_a_directory — tell user the specified path is not a valid directoryIf total_public_items is 0:
Stop here if error or nothing found.
Show overall coverage from overall_coverage:
Show coverage by type from by_type:
Show coverage by directory from by_directory:
List items from the undocumented array, grouped and prioritized:
For each item show: name, file path, and line number.
Also show partial items (have inline docs but no dedicated doc page).
For high-priority undocumented items, offer to:
When generating stubs:
After generating stubs, summarize:
npx claudepluginhub ekline-io/ekline-docs-skills --plugin ekline-docs-skillsDetects missing XML docs in C#, docstrings in Python, JSDoc in JS/TS, and CHANGELOG gaps. Produces coverage reports with gaps by file/symbol for pre-PR validation and CI.
Generates documentation in three modes: function-level (JSDoc/docstrings), module-level (directory READMEs), and API reference (endpoints/exports). Reads and matches existing project doc style.