reverse

Reverse-engineer codebases to generate spec.md and arch.md documentation.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Marunion/ai-factbomb --skill reverse-marunion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse
Source: https://github.com/Marunion/ai-factbomb/tree/main/archflow-main/skills/reverse
Command: npx skills add https://github.com/Marunion/ai-factbomb --skill reverse-marunion

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of essential documentation (spec.md, arch.md) from existing codebase, saving significant manual effort and ensuring up-to-date records.

Core Features & Use Cases

  • Reverse Engineering: Analyzes code to generate spec.md (requirements) and arch-be.md/arch-fe.md (architecture).
  • Automated Documentation: Reduces the burden of manual documentation for legacy or undocumented systems.
  • Use Case: You have a legacy backend service with no documentation. Use this Skill to analyze its codebase, infer its purpose, map its API endpoints, and generate initial spec.md and arch-be.md files.

Quick Start

Use the reverse skill to generate documentation for the 'alert' service backend code.

Frequently Asked Questions about reverse

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

FAQPage Schema
How do I generate documentation for a legacy codebase with no existing specs?

To generate documentation for a legacy codebase, you can reverse-engineer the existing code to automatically extract API specifications, database schemas, and component structures, producing initial spec.md and arch.md files.

Can I extract API specifications and database schemas from existing backend code?

Yes, you can extract API specifications and database schemas from existing backend code by analyzing the codebase to infer business goals and map endpoints, which are then compiled into structured arch-be.md documentation.

Does automated reverse engineering work for both frontend and backend code analysis?

Automated reverse engineering works for both frontend and backend code analysis, extracting component structures and APIs to generate corresponding architecture files like arch-fe.md for frontend and arch-be.md for backend systems.

What is the best way to document an undocumented backend service automatically?

The best way to document an undocumented backend service automatically is to reverse-engineer the codebase, analyzing its structure to infer its purpose and outputting comprehensive spec.md and arch-be.md files without manual effort.

How do I turn code into architecture and requirements documentation?

To turn code into architecture and requirements documentation, reverse-engineer the codebase to analyze its components and APIs, generating a spec.md file for requirements and arch.md files for architecture.