codebase-scanner

Analyze project source code to identify languages, frameworks, and toolchain components.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill codebase-scanner-emeaappgbb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-scanner
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/codebase-scanner
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill codebase-scanner-emeaappgbb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, unbiased inventory of your project's technology footprint, allowing you to understand your existing infrastructure before any migration or modernization work begins.

Core Features & Use Cases

  • Project Structure Scan: Document file extensions, directory conventions, and entry points.
  • Language Detection: Identify the programming languages and frameworks in use.
  • Build Tool Identification: List package managers, bundlers, compilers, and other toolchain components.
  • Use Case: Before upgrading a legacy application, use this Skill to get a clear picture of the technologies involved and their interdependencies.

Quick Start

Run the codebase-scanner skill on your project's root directory to generate a technology stack report in 'specs/docs/technology/stack.md'.

Frequently Asked Questions about codebase-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory a codebase for technology stack analysis before modernization?

To inventory a codebase for technology stack analysis, run the scanner on your project's root directory to traverse the file tree and parse configuration files, generating a comprehensive technology stack report.

What is codebase inventory and when do I need it for technical debt management?

Codebase inventory is the process of identifying programming languages, frameworks, and toolchain components in a project. You need it for technical debt management to understand existing infrastructure before any migration begins.

Can I detect programming languages and build tools without configuring a project assessment?

Yes, you can detect programming languages and build tools with zero assessment. The scanner identifies package managers, bundlers, and compilers by parsing configuration files directly from the source code.

Does the codebase analysis work with any project structure or directory convention?

The codebase analysis works with any project structure by documenting file extensions, directory conventions, and entry points. It requires file tree traversal to accurately map the technology footprint.

What's the best way to identify frameworks and toolchain components in a legacy application?

The best way to identify frameworks and toolchain components in a legacy application is running an unbiased source code scan. It lists package managers and compilers to provide a clear picture of technology interdependencies.

Do I need external dependencies to generate a technology stack report for my source code?

No external dependencies are required to generate a technology stack report. The scanner operates independently to inventory your project's technology footprint and outputs the results to a markdown file.