fuzzing-test

# Fuzzing Test Skill (Go) Generate high-signal Go fuzz tests only when targets are suitable. ## Quick Reference — Load References Selectively Read the section named below first; load the reference only when its trigger applies. | When you need to… | Section | Load on demand | |---|---|---| | Decide if a target is suitable | §Applicability Gate (**run first, always**) | `applicability-checklist.md` — full decision tree, oracle forms, version gate, borderline cases | | Choose among 3+ candidate targets | §Target Priority Gate | `target-priority.md` — bug-yield ranking and tie-breaks | | Write the harness | §Minimal Templates | — | | Handle a discovered crash | §Crash Handling | `crash-handling.md` — triage steps, corpus policy, report template | | Set up CI | §CI Strategy | `ci-strategy.md` — Actions config, corpus caching, budgets | | Diagnose a slow/ineffective run, OOM, leak, or flake | §Fuzz Performance Baseline | `advanced-tuning.md` — seed quality, skip-rate, allocation profiling | | Avoid or check for common mistakes | §Quality Scorecard | `anti-examples.md` — 9 BAD/GOOD harness patterns | ## Applicability Gate (Must Run First) Before writing any fuzz code, evaluate suitability. If the target fails this gate, the entire remaining workflow is skipped — output the verdict, suggest alternatives, and stop. Mark each item `Pass` / `Fail`: 1. Target has meaningful input space (not trivial fixed-path logic). 2. Target can be driven by Go fuzz-supported parameter types. ...