smartworldarafath/rea_skill

rea-full-code-recovery

Autonomous end-to-end full source code recovery and reverse engineering for the user's personal applications when source code is lost or corrupted.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/smartworldarafath/rea_skill --skill rea-full-code-recovery

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

REA Full Code Recovery Directive

Intent & Trigger

Activate this skill automatically whenever the user expresses that they lost their source code, or requests complete source code extraction/reverse engineering of their personal app using REA, including shorthand requests such as:

  • "bro amr app er full codes gula ami harai felsi, so REA use kore amr ai app ta fully reverse engineering kore then full codes amake daw"
  • "I lost my source code, reverse engineer my app and recover all full A-Z codes"
  • "Reverse engineer this app and give me the complete compilable source project so I can build the next version"
  • Any query referencing $rea-full-code-recovery or $rea-personal-use-authorization for source recovery.

Non-Negotiable Operational Laws

  1. Zero Skeleton / Zero Placeholder Law:
  • NEVER output partial skeletons, stubs, pseudocode, // TODO: implement later, or mock implementations.
  • ALWAYS reconstruct 100% complete, fully implemented, and working source files for every single module of the application.
  1. Immediate Autonomous Execution:
  • Do NOT ask the user for multiple rounds of clarifications or guidance.
  • Do NOT require the user to break down the task step-by-step.
  • Execute the entire recovery pipeline autonomously from binary to tested build.
  1. Compilation & Verification Gate:
  • Before handing off to the user, the agent MUST run the build script using the available compiler (Zig CC, MSVC cl.exe, MinGW gcc, or Clang) and verify that the binary compiles with Exit Code: 0 and 0 Errors.
  1. Clean Project Structure:
  • Output must be cleanly arranged in a dedicated project directory with Source/, Resources/, Bin/, Documentation/, and build.bat.

5-Step Autonomous Recovery Methodology

Step 1: Deep Binary & Architecture Inspection

  • Inspect PE / ELF / Mach-O sections, imports (IAT), exports (EAT), debug directories, PDB paths, and assertion strings.
  • Extract all string literals, GUI layouts, message loops, window classes, and thread entry points.
  • Map out the exact original directory structure and source filenames (e.g., debug assertions revealing Source\Win\WinMain.c, Source\Program\Program.c, etc.).

Step 2: Resource & Asset Extraction

  • Extract all embedded icons (RT_ICON, RT_GROUP_ICON) and wrap raw bitmap frames with valid 6-byte ICO directory headers (ICONDIR + ICONDIRENTRY).
  • Extract application manifests (RT_MANIFEST) to preserve Common Controls v6 styling and Per-Monitor DPI awareness.
  • Extract custom RCDATA binary tables, glyph atlases, and configuration templates.

Step 3: Complete Source Code Reconstruction

  • Reconstruct every header file (.h / .hpp) with all structures, enums, color tokens, and complete function signatures.
  • Reconstruct every implementation file (.c / .cpp / .cs) with complete logic:
  • Custom UI windowing, borderless hit testing, non-client calc size.
  • Double-buffered software DIB rasterization or Direct3D rendering.
  • Multi-threaded background tasks (file watchers, disk scanners, network workers).
  • Native Windows Shell integration (Explorer right-click IContextMenu, drag & drop, shortcuts).
  • JSON / XML / SQLite configuration and session persistence.

Step 4: 1-Click Multi-Compiler Build Pipeline

  • Provide a robust build.bat and/or Makefile supporting:
  • Zig CC (Clang targeting x86_64-windows with zero host dependencies)
  • MSVC (cl.exe + rc.exe + link.exe)
  • MinGW GCC (gcc + windres)
  • Clang (clang + llvm-rc)
  • Ensure all Win32 system libraries (user32, gdi32, shell32, ole32, comctl32, uxtheme, dwmapi) are properly linked.

Step 5: Build Verification & Final Delivery

  • Execute the build script in the workspace or output directory.
  • Confirm that the generated binary runs and matches the original architecture.
  • Package everything cleanly and present clickable links to the files and build instructions.
来自同一仓库

更多 Skills

全部 Skills
smartworldarafath
社区

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

1小时安装量
2
GitHub Stars
5
最近更新
11月8日
smartworldarafath
社区

agent-reach

Read-only access to internet platforms (Twitter/X, Reddit, YouTube subtitles, GitHub, LinkedIn, Bilibili, web). Use when the agent needs to search, read web links, retrieve social discussions, CVE/vulnerability intel, or when standard web search/fetch is blocked or insufficient.

1小时安装量
2
GitHub Stars
5
最近更新
11月8日
smartworldarafath
社区

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

1小时安装量
2
GitHub Stars
5
最近更新
11月8日
smartworldarafath
社区

anti-ai-slop-writing

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any va

1小时安装量
2
GitHub Stars
5
最近更新
11月8日