repo-scan

Audits cross-stack source code to classify files, detect embedded third-party libraries, and generate HTML reports.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill repo-scan-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/repo-scan
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill repo-scan-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When taking over a large legacy codebase or monorepo, it is hard to know how much code is actually yours, what third-party libraries are embedded directly in source, and what is dead weight. This Skill scans C/C++, Android, iOS, and Web codebases in one pass to answer those questions with actionable per-module verdicts. ## Core Features & Use Cases - Cross-stack file classification: Tags every file as project code, embedded third-party code, or build artifact across C/C++, Java/Android, iOS (OC/Swift), and Web (TS/JS/Vue). - Embedded library detection: Identifies 50+ known libraries such as FFmpeg, Boost, and OpenSSL with version extraction, even when not declared in package managers. - Four-level module verdicts: Assigns Core Asset, Extract & Merge, Rebuild, or Deprecate per module, delivered in interactive dark-theme HTML reports with drill-down navigation. - Use Case: Auditing a 50,000-file C++ monorepo before refactoring to find outdated vendored dependencies, duplicated SDK wrappers, and hundreds of MB of committed build artifacts. ## Quick Start Ask the agent to run a standard-depth repo-scan audit on your repository and produce the interactive HTML report with per-module verdicts.

Frequently Asked Questions about repo-scan

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

FAQPage Schema
How do I audit a large legacy codebase for third-party code?▼

Run a standard-depth scan that enumerates every file and tags it as project code, embedded third-party code, or build artifact. The audit detects 50+ known libraries like FFmpeg, Boost, and OpenSSL by inspecting directory names, headers, and license files.

How to detect vendored dependencies not declared in package managers?▼

The scanner inspects directory names, header files, license files, and version markers to identify bundled dependencies and their likely versions. This catches libraries copied directly into source trees that tools like npm or Maven never see.

What languages and platforms does repo-scan support?▼

It scans C/C++, Java/Android, iOS (Objective-C and Swift), and Web (TypeScript, JavaScript, Vue) in a single pass. Monorepos are supported with hierarchical scanning that produces a summary report plus per-sub-project reports.

Which analysis depth level should I use for a monorepo?▼

Start with fast depth for monorepos with 100+ modules to get a quick inventory reading 1-2 files per module. Use standard for a default audit, deep for modules flagged for refactoring, and full for pre-merge comprehensive reviews.

What are the limitations of source-level dependency detection?▼

Detection relies on directory names, headers, licenses, and version markers, so heavily modified or stripped vendored code may not be identified. Version extraction is a best-effort estimate and should be verified before making upgrade decisions.