ruzzy

Fuzz Ruby applications and C extensions to uncover memory-safety issues and crash-inducing inputs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DobricLilujun/LabAgentSkill --skill ruzzy-dobriclilujun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ruzzy
Source: https://github.com/DobricLilujun/LabAgentSkill/tree/main/skillsHub/skills_scaling/testing-handbook-skills/skills/ruzzy
Command: npx skills add https://github.com/DobricLilujun/LabAgentSkill --skill ruzzy-dobriclilujun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fuzz Ruby applications and C extensions to uncover memory-safety issues and crash-inducing inputs.

Core Features & Use Cases

  • Coverage-guided fuzzing for Ruby code and Ruby C extensions with sanitizer support
  • Deterministic harness templates and reproducible campaigns
  • CI-friendly workflows for crash discovery and diagnostics

Quick Start

Install Ruzzy via gem with sanitizer support and run your fuzzing harness to begin fuzzing.

Frequently Asked Questions about ruzzy

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

FAQPage Schema
How do I fuzz Ruby C extensions to find memory-safety bugs?

Fuzz Ruby C extensions by running coverage-guided fuzzing campaigns with sanitizer-enabled builds to uncover memory-safety issues and crash-inducing inputs. Ruzzy provides harness templates and deterministic workflows to produce actionable crash diagnostics.

What is coverage-guided fuzzing for Ruby applications?

Coverage-guided fuzzing for Ruby applications is a crash-testing technique that feeds varied inputs into a harness to uncover memory-safety issues. It uses sanitizer support and deterministic workflows to generate reproducible crash inputs during QA or research.

Can I run Ruby fuzzing campaigns in a CI pipeline?

Yes, you can run Ruby fuzzing in CI pipelines. Ruzzy supports CI-friendly workflows for crash discovery and diagnostics, allowing automated fuzzing of pure Ruby code and native extensions during continuous integration testing.

Do I need sanitizer-enabled builds to fuzz Ruby native extensions?

Sanitizer-enabled builds are required to effectively fuzz Ruby native extensions for memory-safety issues. Ruzzy supports sanitizer integration to detect memory violations and produces deterministic crash inputs for actionable diagnostics.

How do I create a reproducible fuzzing harness for Ruby code?

Create a reproducible fuzzing harness for Ruby code using deterministic harness templates. Ruzzy provides these templates alongside sanitizer-enabled builds to ensure fuzzing campaigns produce consistent, reproducible crash inputs and actionable diagnostics.