repo-scan

Classify repository files and detect embedded third-party libraries across C/C++, Java/Android, iOS, and Web codebases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill repo-scan-maelwalser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/repo-scan
Command: npx skills add https://github.com/Maelwalser/claude-config --skill repo-scan-maelwalser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large, multi-language codebases often contain embedded third-party libraries, duplicated wrappers, and committed build artifacts that obscure ownership and increase maintenance cost; repo-scan provides a structural inventory and remediation guidance so teams can quickly understand what code is truly theirs and what should be extracted, rebuilt, or removed.

Core Features & Use Cases

  • Cross-stack scanning: single-pass analysis for C/C++, Java/Android, iOS (Objective-C/Swift), and Web (TS/JS/Vue).
  • File classification: tag files as project code, third-party (vendored), or build artifacts and quantify their size and impact.
  • Library detection & versioning: recognize common embedded libraries and extract likely version markers from headers and license files.
  • Verdicts & reports: assign four-level remediation verdicts (Core Asset / Extract & Merge / Rebuild / Deprecate) and produce interactive dark-theme HTML reports with per-module drill-down.
  • Use Cases: takeover audits for legacy repos, pre-refactor dependency inventories, and monorepo cleanups to identify dead weight and duplication.

Quick Start

Run repo-scan to produce an interactive HTML audit that classifies files, detects vendored libraries, and summarizes remediation actions.

Frequently Asked Questions about repo-scan

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

FAQPage Schema
How do I detect vendored third-party libraries in a legacy monorepo?

You can audit a legacy monorepo to find vendored third-party libraries by running a cross-stack source scan that recursively enumerates files, inspects license headers, and extracts version markers to classify embedded dependencies across multiple programming languages.

What is the best way to inventory dead code and build artifacts before refactoring a codebase?

Inventorying dead code and build artifacts before a refactor requires scanning repository files to tag project code, third-party vendored libraries, and committed artifacts, then generating interactive HTML reports with per-module drill-down and four-level remediation verdicts.

Does cross-stack code auditing work for mixed C/C++, Java, iOS, and Web codebases?

Cross-stack code auditing works for mixed C/C++, Java/Android, iOS (Objective-C/Swift), and Web (TS/JS/Vue) codebases. It performs single-pass analysis to classify files, detect embedded libraries, and quantify size impacts across these distinct technology stacks.

How do I identify duplicated wrappers and committed build artifacts in a multi-language codebase?

Identifying duplicated wrappers and committed build artifacts in a multi-language codebase involves structural inventory scanning that tags files as project code, third-party, or build artifacts, assigning remediation verdicts like Extract & Merge or Deprecate to guide cleanup.

Can I generate an interactive HTML report for a repository dependency audit?

You can generate an interactive dark-theme HTML report for a repository dependency audit. The report provides per-module drill-down capabilities and summarizes remediation actions with four-level verdicts: Core Asset, Extract & Merge, Rebuild, or Deprecate.