reversa-scout

Map legacy project structure, technologies, entry points, and CI/CD signals into inventory files.

Updated May 5, 2026
One-click install
npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-scout-alexandrepontesjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-scout
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-scout
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-scout-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Acelera a engenharia reversa ao transformar um projeto legado em um inventário estruturado, reduzindo o tempo gasto entendendo pastas, tecnologias, pontos de entrada e dependências antes de qualquer refatoração.

Core Features & Use Cases

  • Mapeamento da superfície do sistema: gera uma árvore de diretórios (com exclusões) e identifica linguagens, frameworks e bibliotecas com base em arquivos do repositório.
  • Descoberta de pontos de entrada: localiza entry points, configurações e pistas de execução (incluindo CI/CD e Docker, quando existentes).
  • Saída para agentes downstream: cria inventory.md, dependencies.md e um surface.json no formato consumido por outros agentes, incluindo uma sugestão de organização das specs.

Quick Start

Execute o Scout para gerar o inventário e o surface.json a partir do projeto legado, usando o output_folder e doc_level definidos em .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 map a legacy project structure for a reverse engineering inventory?

Mapping a legacy project structure involves inventorying the directory tree, technologies, and entry points to generate a structured project surface. This process produces deterministic outputs like an inventory file and a surface.json schema to accelerate onboarding.

What is codebase reconnaissance and when do I need it for legacy modernization?

Codebase reconnaissance is the initial first-pass scanning of a legacy system to understand its directory layout, frameworks, and CI/CD signals before deeper analysis. You need it to reduce onboarding time and create an actionable inventory prior to any refactoring.

Does dependency mapping in a legacy codebase also detect CI/CD signals?

Dependency mapping in this context detects CI/CD signals by locating execution hints, configurations, and Docker files when they exist. It identifies languages, frameworks, and libraries based on repository files to build a complete project inventory.

What is the best way to generate a project inventory for downstream agents?

The best way to generate a project inventory for downstream agents is producing a surface.json schema alongside inventory.md and dependencies.md. This structured surface discovery output enables other agents to consume the mapped legacy system data deterministically.

What are the limitations of surface discovery for legacy modernization?

Surface discovery limitations include providing only a superficial first-pass understanding rather than deep code analysis. It maps directory structures and database hints but does not perform the deeper reverse engineering required for actual refactoring.