Classify project-owned code, embedded libraries, and build artifacts across technology stacks.
npx skills add https://github.com/panamini/pi-tooling --skill repo-scan-panamini
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
repo-scan eliminates the uncertainty of what code in a large project is truly yours versus vendored, duplicated, or dead weight.
Run a repository audit by asking the assistant to scan the codebase at standard depth and return an HTML report with per-module verdicts.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Proxy2021Scan local filesystems to identify software projects and infer tech stacks.
pdovhomiljaDocument the project's technology stack, listing frameworks, databases, and third-party services.
ZESCODEAudit source code across C++, Android, iOS, and Web ecosystems.
haibindevAudit cross-stack monorepos and classify files into project code, dependencies, and build artifacts.
