repo-scan

Audit cross-stack monorepos and classify files into project code, dependencies, and build artifacts.

22|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/haibindev/repo-scan --skill repo-scan-haibindev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/haibindev/repo-scan/tree/main
Command: npx skills add https://github.com/haibindev/repo-scan --skill repo-scan-haibindev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of understanding large multi-technology-stack monorepos where single-stack tools cannot distinguish core project code from third-party libraries and dead weight. It delivers a unified cross-stack source code asset audit that classifies every file, identifies dependencies, and provides actionable verdicts for each module.

Core Features & Use Cases

  • Cross-stack unified view: Audits C/C++, Java/Android, iOS, C#/.NET, and Web projects in a single pass.
  • Three-way file classification: Separates project code, third-party libraries, and build artifacts with accurate size metrics.
  • Four-level verdicts: Assigns each module a decision: Core Asset, Extract & Merge, Rebuild, or Deprecate.
  • Interactive HTML reports: Generates dark-theme local pages with drill-down project cards and verdict distribution bars.

Quick Start

Use the repo-scan skill to audit the source code directory at /path/to/your/project and generate a comprehensive asset audit report with module-level 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 source code assets in a multi-technology monorepo?

Source code asset audits in a multi-technology monorepo classify files into project code, third-party dependencies, and build artifacts across C++, Java, iOS, C#, and Web stacks. This unified cross-stack view identifies over 50 known libraries and provides actionable architectural decisions.

How can I distinguish third-party dependencies from project code in mixed-stack repositories?

Distinguishing third-party dependencies from project code in mixed-stack repositories requires a cross-stack unified view that parses C++, Java/Android, iOS, C#/.NET, and Web files. The audit extracts version information and separates core assets from external libraries.

What is the best way to triage source code modules for architectural decision-making?

The best way to triage source code modules for architectural decision-making is generating four-level verdicts: Core Asset, Extract & Merge, Rebuild, or Deprecate. These classifications separate project code from dead weight and pinpoint modules needing action.

Does cross-stack source code auditing work for C++, Java, and Web projects in a single pass?

Cross-stack source code auditing works for C++, Java/Android, iOS, C#/.NET, and Web projects in a single pass. It delivers a unified view by scanning the entire monorepo directory and classifying every file with accurate size metrics.

How do I generate an interactive HTML report for a monorepo source code audit?

To generate an interactive HTML report for a monorepo source code audit, run the scan on your project directory. It produces dark-theme local pages with drill-down project cards and verdict distribution bars for visual architectural analysis.

What are the limitations of single-stack tools when auditing monorepos with multiple technology stacks?

Single-stack tools face limitations when auditing monorepos with multiple technology stacks because they cannot distinguish core project code from third-party libraries across different languages. A cross-stack unified audit is required to classify files and identify dependencies accurately.