What problem does it solve? Ruby lacks production-ready coverage-guided fuzzing tools, making it hard to detect memory corruption, undefined behavior, and crashes in Ruby applications and native C extensions before they reach production. ## Core Features & Use Cases - Pure Ruby Fuzzing: Uses a tracer-and-harness script pattern to coverage-guide fuzzing of pure Ruby code. - C Extension Fuzzing: Fuzzes Ruby gems with native extensions using AddressSanitizer and UndefinedBehaviorSanitizer to detect heap overflows, use-after-free, and integer overflow. - libFuzzer Integration: Passes all standard libFuzzer options (max_len, timeout, corpus directories) and saves crash artifacts for reproduction. - Use Case: Fuzz the msgpack MessagePack parser by compiling the gem with sanitizer flags, writing a harness that calls MessagePack.unpack, and running it under ASan to find memory corruption bugs. ## Quick Start Use the ruzzy skill to write a fuzzing harness for my Ruby C extension and show me how to run it with AddressSanitizer enabled.