Fuzzer Skill

When to Use

Invoke when asked to fuzz a target, find memory/integer bugs via fuzzing, write a fuzz harness, or run a fuzzing campaign on a codebase.

Workflow

Step 1 — Audit (MANDATORY — always run first, no exceptions)

You MUST invoke the audit-context-building skill before writing any harness. Do not skip this step even if you think you already understand the code.

Goal: read the entire codebase — all source files — before ranking anything. Do not stop after finding the first suspicious location in one directory. Cover all modules.