repo-scan
affaan-m/everything-claude-code
Cross-stack source code audit: classify files, detect embedded libraries, deliver actionable verdicts with interactive HTML reports.
What is repo-scan?
repo-scan audits large codebases across C++, Java/Android, iOS, and Web to classify every file as project code, third-party, or build artifact, and detects embedded libraries with version extraction. Use it when taking over legacy code, preparing for refactoring, or auditing undeclared third-party dependencies.
- Cross-stack scanning of C/C++, Java/Android, iOS (OC/Swift), and Web (TS/JS/Vue) in one pass
- File classification as project code, third-party, or build artifact
- Detection of 50+ known libraries (FFmpeg, Boost, OpenSSL, etc.) with version extraction
- Four-level verdicts per module: Core Asset, Extract & Merge, Rebuild, or Deprecate
- Interactive dark-theme HTML reports with drill-down navigation
- Monorepo support with hierarchical scanning and per-project summaries
How to install repo-scan
npx skills add https://github.com/affaan-m/everything-claude-code --skill repo-scan- Git installed for cloning the skill repository
- Access to the target codebase (local or mounted)
How to use repo-scan
- 1.Run repo-scan with desired depth level (fast, standard, deep, or full)
- 2.Review the generated HTML report in your browser for module-level verdicts and cross-stack analysis
- 3.Drill down into flagged modules to inspect file classifications and detected libraries
- 4.Use the summary to prioritize refactoring: extract duplicates, rebuild outdated vendored code, or deprecate dead weight
- 5.Share the interactive report asynchronously with stakeholders for architecture decisions
Use cases
- Taking over a large legacy codebase to understand structural composition and ownership
- Identifying embedded third-party libraries and outdated vendored code before refactoring
- Discovering duplicate wrappers and dead-weight build artifacts across monorepos
- Preparing architecture decision records for monorepo reorganization
- Pre-merge comprehensive review of code quality and dependency risks
- Engineering leads auditing legacy systems
- Architects planning refactoring or monorepo reorganization
- DevOps/build engineers managing multi-stack codebases
- Teams inheriting unfamiliar or undocumented projects
repo-scan FAQ
fast reads 1-2 files per module for quick inventory; standard (default) reads 2-5 files for full dependency and architecture checks; deep reads 5-10 files adding thread safety and memory analysis; full reads all files for comprehensive pre-merge review.
Yes. repo-scan supports hierarchical scanning with a summary report plus individual sub-project reports for drill-down analysis.
Core Asset (keep and maintain), Extract & Merge (consolidate duplicates), Rebuild (modernize outdated code), and Deprecate (remove or replace).
Yes, it inspects directory names, headers, license files, and version markers to identify 50+ known libraries and extract their likely versions.
A concise summary plus interactive HTML reports with dark theme and per-module drill-down navigation for asynchronous review.
Full instructions (SKILL.md)
Source of truth, from affaan-m/everything-claude-code.
name: repo-scan description: Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports. metadata: origin: community
repo-scan
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.
When to Use
- 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
Installation
# Fetch only the pinned commit for reproducibility
mkdir -p ~/.claude/skills/repo-scan
git init repo-scan
cd repo-scan
git remote add origin https://github.com/haibindev/repo-scan.git
git fetch --depth 1 origin 2742664
git checkout --detach FETCH_HEAD
cp -r . ~/.claude/skills/repo-scan
Review the source before installing any agent skill.
Core Capabilities
| 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 |
| Monorepo support | Hierarchical scanning with summary + sub-project reports |
Analysis Depth Levels
| Level | Files Read | Use Case |
|---|---|---|
fast | 1-2 per module | Quick inventory of huge directories |
standard | 2-5 per module | Default audit with full dependency + architecture checks |
deep | 5-10 per module | Adds thread safety, memory management, API consistency |
full | All files | Pre-merge comprehensive review |
How It Works
- Classify the repo surface: enumerate files, then tag each as project code, embedded third-party code, or build artifact.
- Detect embedded libraries: inspect directory names, headers, license files, and version markers to identify bundled dependencies and likely versions.
- Score each module: group files by module or subsystem, then assign one of the four verdicts based on ownership, duplication, and maintenance cost.
- Highlight structural risks: call out dead-weight artifacts, duplicated wrappers, outdated vendored code, and modules that should be extracted, rebuilt, or deprecated.
- Produce the report: return a concise summary plus the interactive HTML output with per-module drill-down so the audit can be reviewed asynchronously.
Examples
On a 50,000-file C++ monorepo:
- Found FFmpeg 2.x (2015 vintage) still in production
- Discovered the same SDK wrapper duplicated 3 times
- Identified 636 MB of committed Debug/ipch/obj build artifacts
- Classified: 3 MB project code vs 596 MB third-party
Best Practices
- Start with
standarddepth for first-time audits - Use
fastfor monorepos with 100+ modules to get a quick inventory - Run
deepincrementally on modules flagged for refactoring - Review the cross-module analysis for duplicate detection across sub-projects
Links
Related skills
More from affaan-m/everything-claude-code and the wider catalog.
security-review
Security checklist and patterns for authentication, input validation, secrets, and sensitive features.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable applications.
coding-standards
Baseline coding conventions for naming, readability, immutability, and quality across projects.
frontend-patterns
React and Next.js patterns for components, state management, performance, and modern frontend practices.
backend-patterns
REST/GraphQL API design, database optimization, and server-side patterns for Node.js, Express, and Next.js.
golang-testing
Go testing patterns: table-driven tests, subtests, benchmarks, fuzzing, and TDD methodology.