reversa-scout

Map legacy-code surfaces by enumerating project folders, languages, frameworks, dependencies, and entry points.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill mapeia a superfície de um projeto legado, identificando a estrutura de pastas, linguagens, frameworks, dependências e entry points para criar o inventário inicial para engenharia reversa.

Core Features & Use Cases

  • Levanta a árvore do projeto, excluindo diretórios irrelevantes como node_modules, .git, .reversa, dist etc.
  • Identifica linguagens, frameworks e dependências a partir de arquivos de configuração para fornecer um inventário confiável.
  • Fornece diretrizes de saída com base no estado de .reversa/state.json para facilitar a organização do trabalho de engenharia reversa.

Quick Start

Use o reversa-scout para mapear a superfície do sistema legado e gerar o inventário inicial.

Frequently Asked Questions about reversa-scout

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

FAQPage Schema
How do I map the surface of a legacy codebase for reverse engineering?

To map a legacy codebase, enumerate project folders, languages, frameworks, dependencies, and entry points. This process creates a comprehensive inventory for initial reverse engineering analysis.

How do I inventory project dependencies and frameworks from configuration files?

Inventory project dependencies and frameworks by parsing configuration files. This identifies the tech stack and external libraries, providing a reliable baseline for understanding the project's architecture.

What is the best way to identify entry points when reverse engineering legacy code?

Identifying entry points in legacy code involves scanning the project structure to locate main execution files or initialization scripts. This reveals where the application begins its execution flow.

Does mapping project structure automatically exclude irrelevant directories like node_modules?

Mapping project structure automatically excludes irrelevant directories such as node_modules, .git, .reversa, and dist. This ensures the inventory focuses only on the relevant source code and configuration files.

How do I configure output directories for a codebase inventory task?

Configure output directories for a codebase inventory by reading the .reversa/state.json file for output guidelines. Results are then written to the designated _reversa_sdd directory.

Can I use this approach to generate a codebase inventory for any programming language?

You can generate a codebase inventory across multiple programming languages. The approach identifies languages and frameworks from configuration files, making it adaptable to diverse legacy codebases.