Menu
Run cargo-fuzz targets with proper nightly toolchain and options
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | run-fuzz |
| description | Run cargo-fuzz targets with proper nightly toolchain and options |
Run fuzz tests against the scanner's parsing and decoding logic.
run-fuzz <target> - Run specific fuzz target (default 10,000 runs)run-fuzz <target> <runs> - Run with custom iteration countrun-fuzz all - Run all targets briefly (1,000 runs each)run-fuzz list - List available targets| Target | Tests |
|---|---|
fuzz_anchor_soundness | Anchor extraction correctness |
fuzz_b64_gate_build_and_scan | Base64 gate construction and scanning |
fuzz_b64_gate_determinism | Base64 gate deterministic behavior |
fuzz_b64_gate_differential | Base64 gate differential testing |
fuzz_tiger_chunking | Tiger harness chunking logic |
cd fuzz && cargo +nightly fuzz run <target> -- -runs=10000
cd fuzz
for target in fuzz_anchor_soundness fuzz_b64_gate_build_and_scan fuzz_b64_gate_determinism fuzz_b64_gate_differential fuzz_tiger_chunking; do
echo "Running $target..."
cargo +nightly fuzz run $target -- -runs=1000
done
Crashes are saved to fuzz/artifacts/<target>/. To reproduce:
cargo +nightly fuzz run <target> fuzz/artifacts/<target>/<crash-file>
rustup install nightlycargo install cargo-fuzzWrite-then-verify documentation pipeline. Use when a user asks to improve comments or docs, explain algorithms or design choices, write or upgrade docstrings, or raise documentation quality for a codebase (especially Rust crates). Writes docs, then automatically verifies every claim against code reality using a fresh agent to eliminate confirmation bias.
Use when you have code review findings, PR comments, or review reports that need to be systematically addressed — especially when there are multiple findings across different files and severities
Use when creating any beads task — auto-researches the codebase, links related tasks, and produces a rich self-contained description from a structured template. Accepts minimal intent and outputs a complete task ready for agent implementation.
Use when you have code review findings, PR comments, or review reports that need to be systematically addressed — especially when there are multiple findings across different files and severities
Use when a task needs an implementation plan that is iteratively created and stress-tested through review-and-revise cycles before implementation begins — catches blind spots, incorrect codebase assumptions, unnecessary complexity, and performance pitfalls while changes are still cheap
Use when a markdown plan file exists and needs validation before implementation — catches design flaws, logic holes, footguns, unnecessary complexity, and performance concerns while changes are still cheap