repo-scan

Audit codebases to classify files, detect libraries, and generate HTML reports.

7|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Davie521/claude-skills --skill repo-scan-davie521
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/Davie521/claude-skills/tree/main/plugins/dev-workflow/skills/repo-scan
Command: npx skills add https://github.com/Davie521/claude-skills --skill repo-scan-davie521

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool audits codebases to identify ownership, embedded libraries, and dead-weight modules across C/C++, Android, iOS, and Web.

Core Features & Use Cases

  • Cross-stack scanning across C/C++, Android, iOS, and Web to map project code, third-party components, and build artifacts.
  • File classification: tag files as project code, third-party, or build artifact.
  • Library detection: identify bundled dependencies and extract versions from source files.
  • Four-level verdicts: Core Asset, Extract & Merge, Rebuild, Deprecate for modules.
  • HTML reports: interactive per-module drill-down reports.
  • Monorepo support: hierarchical summaries with per-module reports.

Quick Start

Install the tool, point it at your repository, and review the generated per-module HTML report.

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 legacy codebase to identify ownership and dead-weight modules?

You can audit a large monorepo by running a cross-stack scan that generates hierarchical summaries and interactive HTML reports for each module. This approach maps project code, third-party components, and build artifacts across C/C++, Android, iOS, and Web stacks.

Can I detect embedded third-party libraries and extract versions from source files across different languages?

Yes, you can detect embedded third-party libraries and extract their versions directly from source files. The cross-language scanning mechanism identifies bundled dependencies across C/C++, Android, iOS, and Web stacks during the codebase audit.

What is the best way to map third-party components and build artifacts in a monorepo?

The best way to map components in a monorepo is using a cross-stack code audit tool that provides hierarchical summaries. It classifies files across C/C++, Android, iOS, and Web, generating interactive per-module HTML drill-down reports for architecture decisions.

Does cross-language codebase scanning work for C/C++, Android, iOS, and Web projects simultaneously?

Cross-language codebase scanning works for C/C++, Android, iOS, and Web projects simultaneously within a single audit. It tags files as project code, third-party, or build artifacts across all these stacks to produce unified per-module classifications.

When do I need to generate four-level module verdicts during a repository refactor?

You need to generate four-level module verdicts when taking over large legacy repositories or making architecture decisions. The verdicts—Core Asset, Extract & Merge, Rebuild, and Deprecate—provide actionable classifications for refactoring projects and managing dead weight.

Are there limitations when scanning monorepos for dead weight across multiple tech stacks?

Limitations when scanning monorepos for dead weight involve the scope of cross-language support, currently focused on C/C++, Android, iOS, and Web. File classification and library detection depend on source file visibility, and build artifacts require explicit tagging.