skills.rest
llmh333
llmh333COMMUNITY
Explore all skills by this author →
GitHub

repo-scan

Classify repository files into project code, embedded third-party, or build artifacts.

Updated Sep 13, 2025
Search Tags:#dependency detection#codebase audit#interactive reports#vendored libraries#monorepo analysis#module risk scoring
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill repo-scan-llmh333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/repo-scan
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill repo-scan-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

repo-scan eliminates the uncertainty of what code in a large repository is truly yours versus bundled third-party code, and it highlights maintenance risk so refactoring decisions are evidence-based.

Core Features & Use Cases

  • Cross-stack source audit: Classifies files across multiple ecosystems (C/C++, Java/Android, iOS, and Web) into project code, embedded third-party, or build artifacts.
  • Embedded library detection: Identifies 50+ known libraries and attempts version extraction from directory/header/license/version markers.
  • Actionable module verdicts: Assigns four-level ownership/maintenance verdicts (Core Asset / Extract & Merge / Rebuild / Deprecate) and generates interactive HTML reports for review.

Quick Start

Use the repo-scan skill to audit the repository for hidden vendored dependencies and produce interactive HTML module verdicts for planning refactors.

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 codebase for hidden vendored dependencies?▼

To audit a codebase for hidden vendored dependencies, scan repository files to classify them as project code, embedded third-party libraries, or build artifacts. This process identifies 50+ known libraries and extracts versions to expose maintenance risks.

What is the best way to triage modules in a large monorepo before refactoring?▼

Triage monorepo modules before refactoring by assigning four-level ownership verdicts: Core Asset, Extract & Merge, Rebuild, or Deprecate. This generates interactive HTML drill-down reports to ensure refactoring decisions are evidence-based.

Can I detect embedded third-party libraries across different tech stacks like C++ and Android?▼

Yes, cross-stack source audits detect embedded third-party libraries across C/C++, Java/Android, iOS, and Web ecosystems. It identifies known libraries and extracts versions from directory, header, license, or version markers.

How does module risk scoring work for legacy takeover and dependency provenance checks?▼

Module risk scoring for legacy takeover works by classifying repository files and assigning four-level verdicts based on ownership and maintenance risk. It checks dependency provenance for vendored code to highlight what is truly yours versus bundled third-party code.

What formats do interactive codebase audit reports support for review?▼

Interactive codebase audit reports are generated as HTML drill-down documents for review. These reports map module verdicts and embedded library detection results to support pre-refactor planning and legacy takeover decisions.

Related Skills

Explore More Software Engineering Skills→
riftzen-bitriftzen-bit

configure-ecc

Install and configure Everything Gemini Code components with verification and optional optimization.

Community
Advanced
bumfobumfo
1

deep-research

Orchestrate parallel web, codebase, and third-party code research with GoT-driven tasks.

Community
Advanced
markus41markus41
18

upgrade-analysis

Analyze source files for upgrade opportunities and code quality issues.

Community
Advanced
dorriodorrio

ln-710-dependency-upgrader

Coordinate dependency upgrades across multiple package managers.

Community
Intermediate