reverse-external-interfaces

To generate external dependency documentation automatically, this Skill scans codebase imports and classifies symbols as system, local, or external, then outputs structured markdown documentation for each external interface with at least one usage.

The best way to map external API usage is by scanning repository references to detect external modules, generating per-interface markdown files and a summary JSON detailing all external interfaces with active call sites.

Reverse engineering external interfaces works by detecting the dominant language in a repository, scanning all import usages, and categorizing symbols to produce structured documentation exclusively for external dependencies.

Yes, you can exclude specific file paths during the external dependency scan. The Skill supports configurable path exclusions and caching to streamline the code analysis process.

Generated external interface docs and summary files are stored under the {REPO_ROOT}/omni-doc/specs/external-interfaces directory, using markdown files prefixed with EXTERNAL-API_ and a EXTERNAL-API_SUMMARY.json file.

Interactive confirmation is optional during external interface documentation generation. The Skill can run autonomously to scan imports and output documentation, but allows manual confirmation if preferred.