repo-scan

Classify repository files and generate interactive HTML audit reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Cross-stack scanning: C/C++, Java/Android, iOS (OC/Swift), Web (TS/JS/Vue) in one pass
  • File classification: Each file tagged as project code, embedded third-party code, 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

Quick Start

Run the repo-scan skill on your codebase to generate an interactive HTML report and per-module audit.

Frequently Asked Questions about repo-scan

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

FAQPage Schema
How do I audit third-party libraries across C++, Android, iOS, and Web codebases?

Third-party library detection scans C++, Android, iOS, and Web codebases to classify files as project code, embedded libraries, or build artifacts, identifying 50+ known libraries like FFmpeg, Boost, and OpenSSL with version extraction.

What is the best way to classify source code assets in a monorepo?

Monorepo-aware scanning performs hierarchical classification of source code assets, generating summary reports for the root project and detailed sub-project reports to support architecture decisions and refactoring.

How does file classification separate project code from build artifacts?

File classification tags each file as project code, embedded third-party code, or build artifact, applying a four-level verdict model—Core Asset, Extract & Merge, Rebuild, or Deprecate—per module to support architecture decisions.

Can I generate interactive HTML reports for code dependency analysis?

Yes, code dependency analysis generates interactive dark-theme HTML reports with drill-down navigation, providing per-module verdicts and library detection results to support dependency management.

Does cross-language scanning work for mixed C++ and Swift monorepos?

Cross-language scanning supports mixed C++ and Swift monorepos by classifying files across ecosystems in one pass, detecting known libraries, and producing hierarchical interactive HTML reports for both root and sub-projects.

When do I need a four-level verdict model for code refactoring?

A four-level verdict model is needed when refactoring complex codebases to classify modules as Core Asset, Extract & Merge, Rebuild, or Deprecate, providing actionable guidance for architecture decisions and dependency management.