reversa-scout

Identify folders, languages, frameworks, dependencies, and entry points in legacy codebases.

1|Updated Nov 20, 2025

Search Tags:#architecture #codebase #dependencies #inventory #reverse-engineering #entry-points #surface-map

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map the surface of a legacy project — enumerating folders, languages, frameworks, dependencies and entry points to create an initial inventory for reverse-engineering analysis.

Core Features & Use Cases

Structure discovery: List top-level and nested directories and identify tech stacks and entry points.
Dependency and entry-point inventory: Analyze configuration and manifest files to capture frameworks, versions, and critical points of integration.
Use Case: At project kickoff, generate a baseline surface inventory to guide engineering effort and risk assessment.

Quick Start

Run the scout to map the current project surface and generate an initial inventory.

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 analysis?▼

To map a legacy codebase for reverse-engineering, analyze directory trees, config files, and metadata to enumerate folders, languages, frameworks, dependencies, and entry points into a structured inventory.

What is the best way to inventory dependencies and entry points across a multi-language project?▼

Inventorying dependencies and entry points across a multi-language project requires analyzing configuration and manifest files to capture frameworks, versions, and critical integration points into a comprehensive baseline list.

Can I generate a structured surface map for a project at kickoff without prior codebase knowledge?▼

Yes, you can generate a structured surface map at project kickoff without prior codebase knowledge by scanning the directory structure and configuration files to produce a baseline inventory for downstream analysis.

Does this approach work for discovering tech stacks and entry points in unfamiliar legacy projects?▼

Yes, this approach works for discovering tech stacks and entry points in unfamiliar legacy projects by analyzing metadata and manifests to identify nested directories, frameworks, and critical points of integration.

What format does the codebase surface inventory output for downstream engineering analysis?▼

The codebase surface inventory outputs a structured format suitable for surface.json, providing a comprehensive baseline to guide engineering effort, risk assessment, and downstream reverse-engineering analysis.