Inventory legacy project structure, technologies, entry points, and CI/CD artifacts.
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-scout-rdinda
Please help me install this Agent Skill. Skill: reversa-scout Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-scout Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-scout-rdinda
This Skill solves the problem of quickly understanding a legacy codebase by mapping its folder structure, technologies, dependencies, entry points, and test signals into an initial, actionable inventory.
Use the reversa-scout skill to generate the initial legacy inventory and surface.json for downstream analysis into the output folder specified by .reversa/state.json.
High-intent search queries and answers about installing and using this skill.
Mapping a legacy codebase involves producing a directory tree, discovering technologies and dependencies, identifying operational entry points like Docker assets and CI/CD, and generating a structured surface.json file for downstream reverse engineering analysis.
Codebase surface mapping is the initial discovery pass that inventories a legacy project's folder structure, technologies, and entry points. You need it when you require an actionable overview before deeper automated engineering analysis.
Finding entry points and CI/CD workflows involves scanning the project for application entry files, configuration files, build scripts, and Docker assets. This operational identification reveals how the system runs and is a core part of surface mapping.
You can estimate test coverage and find database schema hints without running code. The discovery process detects test frameworks and uses a file-count-based estimate, while shallowly listing candidate DDL, migration, and ORM model artifacts for follow-up.
The best way to generate an initial dependency discovery report is to detect languages, frameworks, and package manager clues from configuration files. This produces a comprehensive inventory report alongside a structured surface.json compliant with the surface schema.
The limitation of a shallow surface mapping approach is that database schema hints are only candidate artifacts requiring follow-up by other agents, and test coverage is a lightweight file-count estimate rather than a detailed execution-based metric, serving solely as an initial discovery pass.
sandecoMaps legacy software projects into inventory, dependencies, and surface.json files.
cliffthelinMap legacy project structure, technologies, and entry points into inventory files.
forcedotcomExecute Salesforce Apex unit tests with coverage analysis and failure diagnosis.
stribusIdentify folders, languages, frameworks, dependencies, and entry points in legacy codebases.
