What problem does it solve? Setting up continuous fuzzing infrastructure for open-source projects requires managing Docker images, sanitizer builds, corpus handling, and coverage reporting, which is complex to configure manually. ## Core Features & Use Cases - Local Harness Execution: Build project images, compile fuzzers with sanitizers, and run individual harnesses using the helper.py CLI without hosting the full platform. - Project Enrollment: Create the required project.yaml, Dockerfile, and build.sh files to enroll C/C++, Python, or Rust projects into OSS-Fuzz or a private instance. - Coverage and Bug Analysis: Generate local coverage reports, monitor build statuses, and use Fuzz Introspector to identify fuzzing blockers. - Use Case: You maintain a C++ library and want continuous fuzzing. Use this Skill to write the three enrollment files, test harnesses locally with AddressSanitizer, and submit the project for OSS-Fuzz acceptance. ## Quick Start Help me enroll my open-source C++ project into OSS-Fuzz by creating the project.yaml, Dockerfile, and build.sh files and testing the harness locally.