reverse-engineer

Generate nine documentation files from code analysis with path selection.

1|Updated Jan 24, 2026

Search Tags:#code analysis #documentation #brownfield #reverse engineering #greenfield

Ready to run

npx skills add https://github.com/johan--/stackshift --skill reverse-engineer-johan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-engineer
Source: https://github.com/johan--/stackshift/tree/main/skills/reverse-engineer
Command: npx skills add https://github.com/johan--/stackshift --skill reverse-engineer-johan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the deep analysis of codebases to generate comprehensive documentation, streamlining the reverse engineering process for developers.

Core Features & Use Cases

Comprehensive Documentation: Generates 9 documentation files covering business logic, technical implementation, and system details.
Path-Aware Analysis: Supports both Greenfield (business logic only) and Brownfield (business logic + technical) approaches.
Use Case: For a large legacy application, this Skill can automatically document all business logic and technical implementation details, enabling smooth migration to a new stack.

Quick Start

To initiate the reverse engineering process, run the skill with the path chosen: reverse-engineer --path=greenfield or reverse-engineer --path=brownfield.

Frequently Asked Questions about reverse-engineer

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

FAQPage Schema

How do I automate codebase analysis for generating comprehensive documentation?▼

Automate codebase analysis by running a path-aware process that deeply examines source code and generates 9 comprehensive documentation files covering business logic and technical implementation details.

What is the difference between greenfield and brownfield reverse engineering approaches?▼

Greenfield reverse engineering focuses on extracting and documenting business logic only, whereas the brownfield approach documents both business logic and technical implementation details for a complete system overview.

How do I document legacy application logic to prepare for a stack migration?▼

Document legacy application logic by running automated deep code analysis to map existing business rules and technical implementation, generating structured documentation files that enable smooth migration to a new stack.

Do I need specific code analysis tools to generate technical implementation documentation?▼

Yes, generating technical implementation documentation requires code analysis and documentation generation tools to be present in your environment, as the automation relies on these dependencies to parse and output the 9 files.

Can I choose which aspects of a codebase to analyze for reverse engineering?▼

Yes, you can choose your analysis path by specifying either greenfield for business logic only or brownfield for business logic plus technical details, directly tailoring the documentation output to your project scope.