reversa-scout

Map legacy project structure, languages, frameworks, and entry points.

Updated Feb 27, 2026

Search Tags:#code analysis #project analysis #dependency mapping #reverse engineering #project inventory

Ready to run

npx skills add https://github.com/luisgustavooliveira/skills --skill reversa-scout-luisgustavooliveira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-scout
Source: https://github.com/luisgustavooliveira/skills/tree/main/reversa-scout
Command: npx skills add https://github.com/luisgustavooliveira/skills --skill reversa-scout-luisgustavooliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill creates an inventory of a legacy project's surface, including structure, languages, frameworks, dependencies, and entry points, providing an initial inventory for reverse engineering analysis.

Core Features & Use Cases

Project Inventory: Maps the entire surface of a legacy project.
Technology Identification: Identifies languages, frameworks, and package managers.
Entry Points: Lists application entry points, configuration files, CI/CD pipelines, and Docker configurations.
Database Hints: Provides basic information about database schemas.
Test Coverage: Estimates test coverage based on file counts.
Use Case: Before beginning a reverse engineering analysis, use this Skill to understand the legacy project's structure and dependencies.

Quick Start

Generate the inventory of the legacy project and output it to the default folder using the 'reversa-scout' skill.

Frequently Asked Questions about reversa-scout

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

FAQPage Schema

How do I create an inventory of a legacy project's structure and dependencies?▼

To create an inventory of a legacy project, you can scan directories and parse configuration files to map the structure, languages, frameworks, dependencies, and entry points for reverse engineering analysis.

What is the best way to identify languages and frameworks in an unfamiliar codebase?▼

Identifying languages and frameworks in an unfamiliar codebase requires scanning directories and parsing configuration files to extract technology stacks, package managers, and application entry points.

How do I find application entry points and CI/CD pipelines during reverse engineering?▼

Finding application entry points and CI/CD pipelines during reverse engineering involves parsing configuration files and mapping the project structure to list Docker configurations and initial execution paths.

Can I extract database schema hints and test coverage estimates without running the legacy project?▼

Yes, you can extract database schema hints and estimate test coverage without running the project by scanning directories and counting test files to provide basic database information and coverage estimates.

Does this project inventory approach work for analyzing any technology stack?▼

This project inventory approach works across various technology stacks by scanning directories and parsing configuration files to identify the specific languages, frameworks, and package managers present.

Why do I need to map dependencies before starting a reverse engineering analysis?▼

You need to map dependencies before starting reverse engineering analysis to understand the legacy project's surface, which reveals the structure, external libraries, and database hints required for accurate reconstruction.