skills.rest
Markson22
Markson22COMMUNITY
Explore all skills by this author →
GitHub

reversa-scout

Map legacy system structure, languages, dependencies, and entry points into a surface.json inventory.

Updated Nov 4, 2025
Search Tags:#dependencies#inventory#reverse-engineering#entry-points#architecture-discovery#surface-mapping#legacy-system
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-scout-markson22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-scout
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-scout
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-scout-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps the surface of a legacy system to create a complete inventory of its structure, technologies, dependencies, and entry points, enabling fast reverse-engineering analyses.

Core Features & Use Cases

  • Inventory the project structure (folders and files) while excluding noise folders such as node_modules, .git, .reversa, _reversa_sdd, dist, build, coverage, pycache, .cache
  • Identify languages, frameworks, dependencies, and entry points from configuration files and code
  • Produce a structured surface output to inform planning, risk assessment, and onboarding for legacy migrations

Quick Start

Run the scout at the repository root to map the complete legacy-system surface

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

Mapping a legacy system surface involves inventorying the project structure, languages, dependencies, and entry points. This identifies the technology stack and configuration files, producing a structured surface output for downstream agents.

What is the best way to inventory legacy system architecture and dependencies?▼

Inventorying legacy system architecture involves scanning the repository root to map folders, files, and configuration data while excluding noise directories like node_modules or .git. This generates a complete structured inventory of the project's technologies and dependencies.

Can I use this to identify entry points in a multi-language monolithic stack?▼

Yes, architecture discovery works across monolithic and multi-language stacks. It identifies project entry points and frameworks by parsing configuration files and code, making it suitable for complex legacy environments and risk assessment at project kickoff.

Does the surface mapping exclude build and cache directories during inventory?▼

Yes, the surface mapping automatically excludes noise folders such as node_modules, .git, dist, build, coverage, and __pycache__. This ensures the structured inventory only captures relevant source code and configuration files.

When do I need a structured surface inventory for a software project?▼

You need a structured surface inventory during project kickoff for reverse-engineering analyses, architecture discovery, and risk assessment. It informs planning and onboarding for legacy migrations by providing a complete map of the technology stack and dependencies.

Related Skills

Explore More Software Engineering Skills→
stribusstribus
1

reversa-scout

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

Community
Advanced
sandecosandeco
1.5k

reversa-scout

Maps legacy software projects into inventory, dependencies, and surface.json files.

Community
Intermediate
nicholasgriffintnnicholasgriffintn
2

project-analysis

Analyze a codebase to reveal its structure, dependencies, and architecture.

Community
Basic
DeL-TaiseiOzakiDeL-TaiseiOzaki
190

init

Detect tech stack and commands from project files to update AGENTS.md top sections.

Community
Intermediate