repo-scan

Classify project code, third-party libraries, and build artifacts across C++, Android, iOS, and Web codebases.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill repo-scan-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/repo-scan
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill repo-scan-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Taking over legacy codebases, planning major refactoring, or reorganizing monorepos is hindered by the inability to quickly distinguish between your own project code, embedded third-party dependencies, and useless build artifacts across multiple tech stacks.

Core Features & Use Cases

  • Cross-stack scanning: Supports C/C++, Java/Android, iOS (OC/Swift), and Web (TS/JS/Vue) codebases in a single pass.
  • File and library classification: Tags every file as project code, third-party, or build artifact, and detects 50+ common embedded libraries with version extraction.
  • Actionable module verdicts: Assigns one of four priority levels (Core Asset, Extract & Merge, Rebuild, Deprecate) to each module to guide refactoring and cleanup work.
  • Use Case: For a 50,000-file C++ monorepo, this skill can identify outdated vendored FFmpeg, duplicated SDK wrappers, and hundreds of megabytes of committed build artifacts to prioritize technical debt reduction.

Quick Start

Use the repo-scan skill to run a standard-depth audit of your target codebase and receive an interactive HTML report with per-module asset classifications and refactoring 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 a legacy codebase to identify third-party dependencies and build artifacts?

Cross-stack codebase scanning analyzes C++, Android, iOS, and Web (TS/JS/Vue) source files in a single pass. It evaluates file structures and embedded library signatures to classify assets and identify duplicated SDK wrappers or outdated vendored components across all included stacks.

Can I scan a monorepo containing C++, Android, iOS, and Web codebases at the same time?

Yes, you can scan a cross-stack monorepo containing C++, Android, iOS, and Web codebases in a single pass. The scan tags files across all these platforms simultaneously, identifying project code, third-party dependencies, and build artifacts without requiring separate stack-specific configurations.

What is the best way to classify assets and prioritize refactoring in a large monorepo?

The best way to classify assets for refactoring is assigning per-module four-level verdicts: Core Asset, Extract & Merge, Rebuild, or Deprecate. This approach evaluates file classifications and embedded library versions to produce an interactive HTML drill-down report guiding cleanup priorities.

How do I detect outdated vendored libraries like FFmpeg in a C++ project?

Detect outdated vendored libraries in a C++ project by running a cross-stack codebase scan that recognizes 50+ common embedded libraries with version extraction. The scan identifies outdated vendored FFmpeg and duplicated SDK wrappers to help prioritize technical debt reduction.

Does code audit scanning work for committed build artifact cleanup in Web and mobile repositories?

Code audit scanning works for committed build artifact cleanup by identifying useless generated files across Web and mobile repositories. It classifies these artifacts during the full surface scan, helping eliminate hundreds of megabytes of bloat to reduce technical debt.