skills.rest
ZESCODE
ZESCODECOMMUNITY
Explore all skills by this author →
GitHub

repo-scan

Audit source code across C++, Android, iOS, and Web ecosystems.

Updated Jul 8, 2026
Search Tags:#refactoring#codebase#audit#analysis#monorepo#dependency
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill repo-scan-zescode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/repo-scan
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill repo-scan-zescode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of visibility into large, complex codebases by identifying the true ownership of files, uncovering hidden third-party dependencies, and flagging dead weight or structural risks.

Core Features & Use Cases

  • Cross-stack Scanning: Analyzes C/C++, Java/Android, iOS, and Web projects in a single pass.
  • Four-level Verdicts: Categorizes modules as Core Asset, Extract & Merge, Rebuild, or Deprecate to guide refactoring.
  • Use Case: Use this tool when taking over a legacy monorepo to identify which parts of the code are proprietary, which are outdated vendored libraries, and where build artifacts are bloating the repository.

Quick Start

Run the repo-scan skill on the current directory to generate a comprehensive structural audit 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 large monorepo to identify third-party dependencies and dead code?▼

To audit a large monorepo, you can perform a cross-stack source code scan that classifies files, detects embedded third-party libraries, and flags structural risks across C++, Android, iOS, and Web projects.

What is the best way to classify legacy source code assets for refactoring?▼

The best way to classify legacy source code assets is to use a cross-stack audit that provides four-level module verdicts: Core Asset, Extract & Merge, Rebuild, or Deprecate, guiding your refactoring priorities.

Can I scan C++, Android, iOS, and Web projects in a single pass?▼

Yes, you can scan C++, Android, iOS, and Web projects in a single pass. The audit enumerates project structures and identifies version markers across these ecosystems simultaneously.

How do I detect hidden vendored libraries bloating my codebase?▼

You detect hidden vendored libraries by running a source code audit that uncovers embedded third-party dependencies and flags build artifacts or dead weight bloating the repository.

Do I need file system access to analyze monorepo project structures?▼

Yes, you need file system access to analyze monorepo project structures. The audit requires direct access to enumerate directories and identify version markers for dependency management.

When should I categorize modules as Core Asset or Deprecate during an audit?▼

You should categorize modules as Core Asset or Deprecate when taking over a legacy monorepo, using the audit's verdicts to distinguish proprietary code from outdated vendored libraries and dead weight.

Related Skills

Explore More Software Engineering Skills→
RheasilviaRheasilvia

code-wiki

Generate markdown wikis and Mermaid diagrams from software repositories.

Community
Advanced
betaTridentbetaTrident

repo-scan

Classify source code assets and detect embedded third-party libraries across multi-language monorepos.

Community
Advanced
Sake-TeamSake-Team

repo-scan

Audit source code across C++, Android, iOS, and Web platforms, detecting embedded libraries and generating HTML reports.

Official
Advanced
engalarengalar
1

MDL Syntax Validation Skill

Validate MDL scripts for syntax errors and project reference integrity.

Community
Advanced