repo-scan

Topics in the source

• repo-scan
• When to Use
• Installation
• Core Capabilities
• Analysis Depth Levels
• How It Works
• Examples
• Best Practices

Every ecosystem has its own dependency manager, but no tool looks across C++, Android, iOS, and Web to tell you: how much code is actually yours, what's third-party, and what's dead weight. Taking over a large legacy codebase and need a structural overview Before major refactoring — identify what's core, what's duplicate, what's dead Auditing third-party dependencies embedded directly in source (not declared in package managers) Preparing architecture decision records for monorepo reorganization Review the source before installing any agent skill. Installation completes only the bootstrap. Reload your agent harness, then invoke repo-scan again. This ECC pointer installs the external skill but does not run a scan itself. | Capability | Description | |---|---| | Cross-stack scanning | C/C++, Java/Android, iOS (OC/Swift), Web (TS/JS/Vue) in one pass | | File classification | Every file tagged as project code, third-party, or build artifact | | Library detection | 50+ known libraries (FFmpeg, Boost, OpenSSL…) with version extraction | | Four-level verdicts | Core Asset / Extract & Merge / Rebuild / Deprecate | | HTML reports | Interactive dark-theme pages with drill-down navigation | |

This is an excerpt. Refer to the complete source and its current requirements.