fuzzing-test

Generate and validate Go fuzz tests to surface crashes and regressions.

29|5|Updated Mar 13, 2026

Search Tags:#testing #go #ci #fuzzing #corpus #crash

Ready to run

npx skills add https://github.com/johnqtcg/awesome-skills --skill fuzzing-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fuzzing-test
Source: https://github.com/johnqtcg/awesome-skills/tree/main/skills/fuzzing-test
Command: npx skills add https://github.com/johnqtcg/awesome-skills --skill fuzzing-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generate and validate Go fuzz tests to reliably surface crashes, panics, and regressions in codebases.

Core Features & Use Cases

Applicability gate enforcement to ensure targets are fuzz-worthy before code generation.
Multi-template fuzzing modes: Parser robustness, Round-trip, Differential, and Struct-aware.
Structured seeds, size guards, crash corpus management, and CI-ready workflows.

Quick Start

Copy this skill into your project and activate fuzzing to automatically generate and validate Go fuzz tests against your codebase.

Frequently Asked Questions about fuzzing-test

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

FAQPage Schema

How do I automate Go fuzzing to surface crashes and regressions in my codebase?▼

You can automate Go fuzzing by applying structured workflows with deterministic seeds and controlled corpus management to identify and fuzz code targets, reliably surfacing crashes and regressions across parsing and encoding boundaries.

What is the best way to manage fuzzing corpora and regression inputs for CI in Go?▼

The best way to manage corpora is to use deterministic seeds with size guards and invariant checks, automatically delivering discovered crash inputs as regression tests under the testdata/fuzz directory for CI-ready validation.

Does this fuzzing approach work with multi-parameter workflows and integration boundaries?▼

Yes, this fuzzing approach works across both unit and integration boundaries, applying template-driven harnesses to effectively fuzz multi-parameter workflows, parsing logic, and encoding/decoding routines.

How do you enforce guardrails like size bounds and invariants during Go fuzz testing?▼

Guardrails are enforced by applying size bounds and checking invariants like round-trip consistency or no-panic conditions within template-driven harnesses, ensuring safe and controlled fuzzing execution.

When do I need to use applicability gate enforcement for Go fuzz tests?▼

You need applicability gate enforcement when evaluating whether specific code targets are fuzz-worthy before code generation, ensuring that structured fuzzing modes like Parser robustness or Differential testing are only applied to valid targets.

Can I use differential and round-trip fuzzing modes for Go parsing and encoding tasks?▼

Yes, you can use multi-template fuzzing modes including Parser robustness, Round-trip, Differential, and Struct-aware modes to validate Go parsing and encoding/decoding operations against structured seeds.