repo-scan

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

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/betaTrident/manta --skill repo-scan-betatrident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/betaTrident/manta/tree/main/.agents/skills/repo-scan
Command: npx skills add https://github.com/betaTrident/manta --skill repo-scan-betatrident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the visibility gap in large or legacy codebases by identifying exactly what code is proprietary, what is third-party, and what is dead weight, preventing technical debt accumulation.

Core Features & Use Cases

  • Cross-Stack Classification: Automatically tags files across C++, Java, iOS, and Web stacks as project code, third-party, or build artifacts.
  • Library Detection: Identifies over 50 known embedded libraries and extracts version information to highlight outdated dependencies.
  • Actionable Verdicts: Provides a four-level assessment (Core Asset, Extract & Merge, Rebuild, Deprecate) to guide architectural decisions.

Quick Start

Use the repo-scan skill to perform a standard audit of the current directory and generate an interactive 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 monorepo to identify third-party libraries and technical debt?

To audit a monorepo and identify technical debt, you can scan the source code to classify proprietary assets, detect over 50 embedded third-party libraries, and generate interactive HTML reports detailing module-level verdicts.

What is the best way to prepare a legacy codebase for refactoring?

Preparing a legacy codebase for refactoring involves performing a structural audit to classify source code assets and provide actionable verdicts like Core Asset, Extract & Merge, Rebuild, or Deprecate to guide architectural decisions.

Does dependency analysis work across multi-language stacks like C++, Java, and iOS?

Yes, dependency analysis works across multi-language stacks including C++, Java, iOS, and Web, automatically tagging files as project code, third-party libraries, or build artifacts to highlight outdated dependencies.

How do I detect dead code and outdated embedded libraries in a large codebase?

You can detect dead code and outdated embedded libraries by running a configurable code audit that identifies known third-party dependencies, extracts version information, and flags embedded files as dead weight.

Can I adjust the analysis depth when scanning source code for technical debt?

Yes, you can adjust the analysis depth when scanning source code, allowing the audit to deliver configurable module-level verdicts and interactive HTML reports tailored to your specific technical debt evaluation needs.

What actionable outcomes does a code audit provide for architectural decisions?

A code audit provides actionable outcomes through a four-level assessment system that classifies modules as Core Asset, Extract & Merge, Rebuild, or Deprecate, directly guiding your architectural decisions and refactoring strategy.