reversa-scout

Inventory legacy project structure, technologies, entry points, and CI/CD into markdown and JSON files.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-scout
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-scout
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-scout
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of not knowing what exists inside a legacy codebase by producing an actionable inventory of the project’s structure, technologies, entry points, and basic database surface.

Core Features & Use Cases

  • Legacy surface mapping: Produces a complete directory tree inventory (with well-defined exclusions) to understand what to explore next.
  • Technology and dependency identification: Detects languages, frameworks, critical dependency versions, and package managers from common manifest/config files.
  • Entry-point and integration discovery: Locates application startup points, configuration files, CI/CD definitions, Docker files, and key package scripts.
  • Database and tests (superficial) discovery: Lists DDL/migrations/ORM models if present and estimates test coverage by identifying test frameworks and counting test-spec files.
  • Spec organization suggestion: Generates organization_suggestion for surface.json using heuristics to pick the best granularity (endpoint/module/use-case/hybrid/feature).

Quick Start

Use the reversa-scout skill to generate _reversa_sdd/inventory.md, _reversa_sdd/dependencies.md, and .reversa/context/surface.json for the current legacy project based on .reversa/state.json settings.

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 surface for reverse engineering?▼

Legacy project surface mapping produces an actionable inventory of directory structure, technologies, entry points, and basic database signals. It generates a complete folder tree with defined exclusions to understand what to explore next during reverse engineering reconnaissance.

What is the best way to discover entry points and CI/CD definitions in an unfamiliar codebase?▼

Entry-point discovery locates application startup points, CI/CD definitions, Docker files, and package scripts. It detects languages, frameworks, and critical dependency versions from manifest and configuration files to map integration surfaces.

How do I estimate test coverage and database surface in a legacy codebase?▼

To estimate test coverage and database surface, identify test frameworks, count test-spec files, and list DDL, migrations, or ORM models. This superficial discovery assesses basic testing and database signals without executing the test suite.

Can I generate a structured project inventory from state configuration?▼

Yes, you can generate a structured project inventory by reading a state configuration file and outputting an inventory document, a dependencies document, and a structured surface JSON file following a defined surface schema.

Does legacy surface mapping suggest spec organization granularity?▼

Yes, legacy surface mapping suggests spec organization granularity by generating an organization suggestion. It applies heuristics to pick the best granularity level—endpoint, module, use-case, hybrid, or feature—based on the inventoried project surface.