reversa-scout

Maps legacy project structure, languages, frameworks, and entry points into a structured inventory.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/RLuf/fzagent --skill reversa-scout-rluf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-scout
Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-scout
Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-scout-rluf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a reverse engineering analysis on an unfamiliar legacy codebase is slow and error-prone without an initial inventory. This Skill automates the reconnaissance phase by scanning the project surface and producing structured artifacts that downstream agents and humans can consume. ## Core Features & Use Cases - Project Surface Mapping: Lists the full directory tree (excluding noise like node_modules and .git), counts files by language, and identifies frameworks, package managers, and dependency versions from manifest files. - Entry Point & Infrastructure Detection: Locates application entry files, config files, CI/CD pipelines, Dockerfiles, database schema hints, and test coverage estimates. - Spec Organization Suggestion: Applies ordered heuristics (endpoint, module, use-case, hybrid, feature) to recommend how specs should be organized, with evidence-backed signals. - Use Case: When beginning a reverse engineering engagement on a legacy monorepo, run this Skill first to generate inventory.md, dependencies.md, and a machine-readable surface.json that later analysis agents use as shared context. ## Quick Start Scan this legacy project and generate the initial inventory, dependency report, and surface.json context file in the reversa output folders.

Frequently Asked Questions about reversa-scout

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

FAQPage Schema
How do I create an initial inventory of a legacy codebase?▼

Run a reconnaissance scan that lists the directory tree excluding noise folders, counts files by language extension, and reads manifest files like package.json, requirements.txt, or go.mod to identify frameworks and dependency versions. The results are written to inventory.md and dependencies.md.

How to detect frameworks and entry points in an unknown project?▼

Inspect package manager manifests (package.json, pom.xml, Gemfile, Cargo.toml, composer.json) for frameworks and versions, then look for conventional entry files such as main, index, app, server, or bootstrap, plus CI/CD configs and Dockerfiles.

What is surface.json used for in reverse engineering?▼

surface.json is a structured context file generated during reconnaissance that other analysis agents read. It records languages, frameworks, entry points, modules, and an organization_suggestion field recommending how specs should be grouped.

How does the skill decide how to organize specs?▼

It applies ordered heuristics: centralized routing suggests endpoint granularity, top-level domain folders suggest module, Gherkin or BDD specs suggest use-case, mixed signals suggest hybrid, and no clear signal falls back to feature with extracted feature names.

Does the reconnaissance scan analyze database schemas in depth?▼

No. The scan only lists DDL files, migrations, schemas, and ORM models as surface-level hints in database_hints. Detailed database analysis is delegated to a separate data-focused agent.