repo-scan

Name: repo-scan
Availability: InStock
Author: panamini

Classify project-owned code, embedded libraries, and build artifacts across technology stacks.

Updated May 4, 2026

Search Tags:#monorepo #code audit #architecture review #dependency discovery #risk triage #HTML reporting #vendored libraries

Ready to run

npx skills add https://github.com/panamini/pi-tooling --skill repo-scan-panamini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/panamini/pi-tooling/tree/main/skills/repo-scan
Command: npx skills add https://github.com/panamini/pi-tooling --skill repo-scan-panamini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

repo-scan eliminates the uncertainty of what code in a large project is truly yours versus vendored, duplicated, or dead weight.

Core Features & Use Cases

Cross-stack source audits: Classifies files across C/C++, Java/Android, iOS (OC/Swift), and Web assets in a single pass.
Embedded library detection: Identifies bundled third-party libraries and extracts likely versions from filesystem signals.
Actionable four-level verdicts: Assigns Core Asset / Extract & Merge / Rebuild / Deprecate outcomes per module.
Interactive HTML reporting: Produces drill-down, dark-theme reports suitable for async review.

Quick Start

Run a repository audit by asking the assistant to scan the codebase at standard depth and return an HTML report with per-module 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 monorepo to identify vendored libraries and dead code?▼

To audit a monorepo for vendored libraries and dead code, you need cross-stack source classification to distinguish project-owned files from embedded third-party libraries and build artifacts. This process applies file classification across C/C++, Java, iOS, and Web assets in a single pass.

What is the best way to discover embedded third-party library versions before refactoring?▼

Discovering embedded third-party library versions before refactoring involves scanning filesystem signals to detect bundled libraries and extract likely version numbers. This identifies vendored dependencies requiring risk evaluation during legacy takeover or pre-refactor dependency discovery.

Can I generate an interactive code audit report for a multi-stack repository?▼

Yes, you can generate an interactive code audit report for a multi-stack repository. The process produces drill-down, dark-theme HTML reports suitable for async review, displaying module-level four-tier verdicts across C/C++, Java/Android, iOS, and Web assets.

How does module-level four-tier verdict scoring work for code risk triage?▼

Module-level four-tier verdict scoring for code risk triage works by assigning actionable outcomes—Core Asset, Extract & Merge, Rebuild, or Deprecate—to each module. This classifies code ownership and evaluates vendored-code risk to guide monorepo module assessment.

Does cross-stack file classification support C/C++, Java/Android, iOS, and Web assets simultaneously?▼

Yes, cross-stack file classification supports C/C++, Java/Android, iOS (Objective-C/Swift), and Web assets simultaneously. It audits a repository's source surface in a single pass to classify project-owned code, embedded libraries, and build artifacts across these multiple technology stacks.

When do I need a repository source surface audit for legacy takeover?▼

You need a repository source surface audit for legacy takeover when you must eliminate uncertainty about what code is truly yours versus vendored, duplicated, or dead weight. It applies cross-stack file classification to assess embedded libraries and evaluate vendored-code risk.