Skip to content

lushun2014/lushibo-skills / lushibo-reverse

lushibo-reverse

Verified

Deep reverse engineering for PE, ELF, Mach-O, firmware, drivers, APK/DEX, .NET, Go, Rust, Unity IL2CPP, Unreal, packed binaries, custom VMs, and undocumented protocols. Use when Codex receives a binary, disassembly, pseudocode, crash, native library, game artifact, firmware image, obfuscated application, or needs IDA/Ghidra/Frida/angr/Unicorn automation, algorithm recovery, unpacking, patching, or protocol reconstruction.

references/managed-game.md

View on GitHub
# Managed and Game Targets

## .NET and JVM/Android

Inspect metadata, assemblies/classes, resources, reflection, serializers, JNI/PInvoke boundaries, native libraries, dynamic loading, and runtime-generated code. Use dnSpy/ILSpy/JADX/apktool/JEB/Frida as appropriate.

## Go and Rust

Use runtime signatures, module metadata, string/slice/interface layouts, panic paths, name recovery, and type information. Separate runtime noise from application logic.

## Unity

Determine Mono versus IL2CPP. Correlate `global-metadata.dat`, native modules, class/method indices, generated registration tables, object layouts, transforms, and engine lifecycle methods. Produce typed Frida/C++ stubs when possible.

## Unreal

Identify engine version, UObject/GNames/GObjects patterns, reflection data, class hierarchies, properties, world/actor/component relationships, and serialization/network boundaries.

Always map managed/native transitions and verify offsets against runtime instances.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall