reversa-scout

Map legacy project structure, technologies, dependencies, and entry points into inventory files.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-scout-afsjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-scout
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-scout
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-scout-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of not knowing what a legacy project contains—its folder structure, technologies, dependencies, and entry points—so engineering teams can plan the right next steps for reverse engineering and modernization.

Core Features & Use Cases

  • Project surface mapping: Produces a comprehensive inventory of the legacy codebase by scanning the directory tree and excluding common build/cache artifacts.
  • Technology discovery: Infers languages, main frameworks/libraries, dependency managers, and critical dependency versions from configuration files.
  • Entry point identification: Locates likely application start points, configuration files, CI/CD workflows, Docker setup, and relevant package.json scripts for understanding how the system runs.

Quick Start

Run the reversa-scout skill to generate an initial legacy inventory under the output folder defined in .reversa/state.json.

Frequently Asked Questions about reversa-scout

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

FAQPage Schema
How do I inventory a legacy project's folder structure and tech stack for modernization?

Finding application entry points in an undocumented codebase involves locating start points, configuration files, CI/CD workflows, and dependency versions. This discovers the complete project surface area to help engineering teams plan reverse engineering steps.

What is the best way to map the complete surface area of a legacy system?

The best way to map a legacy system's surface area is performing a single pass scan that excludes build artifacts. It generates a directory tree inventory, infers frameworks, and identifies configuration files to understand how the system runs.

Can I exclude specific folders when scanning a legacy codebase for project inventory?

Yes, you can exclude specified folders when scanning a legacy codebase. The inventory process reads state settings to exclude common build and cache artifacts, ensuring the output only reflects relevant project structure and dependencies.

What files are generated when reverse engineering a legacy project's structure?

When reverse engineering a legacy project, the process generates an inventory markdown file, a dependencies markdown file, and a surface JSON file. These outputs document the directory structure, tech stack, and entry points for modernization planning.

Does legacy modernization planning require knowing the dependency versions beforehand?

Legacy modernization planning benefits from knowing dependency versions beforehand. The inventory process infers languages, frameworks, and critical dependency versions from configuration files to provide the context needed for planning next steps.