.codex/skills/run-fuzz/SKILL.md
Run cargo-fuzz targets with proper nightly toolchain and options
npx skillsauth add ahrav/gossip-rs run-fuzzInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run fuzz tests against gossip-rs data structures and contract types.
/run-fuzz <target> - Run specific fuzz target (default 10,000 runs)/run-fuzz <target> <runs> - Run with custom iteration count/run-fuzz all - Run all targets briefly (1,000 runs each)/run-fuzz list - List available targetsFuzz targets are distributed across crates:
crates/gossip-contracts/fuzz/)| Target | Tests |
|--------|-------|
| fuzz_derivation_chain | Derivation chain construction and validation |
| fuzz_item_identity_key | ItemIdentityKey creation and hashing |
crates/gossip-stdx/fuzz/)| Target | Tests |
|--------|-------|
| fuzz_byte_slab | ByteSlab pool allocation, slot lifecycle |
| fuzz_inline_vec | InlineVec push/pop/access with arbitrary inputs |
| fuzz_ring_buffer | RingBuffer enqueue/dequeue under arbitrary sequences |
cd crates/<crate> && cargo +nightly fuzz run <target> -- -runs=10000
Examples:
cd crates/gossip-stdx && cargo +nightly fuzz run fuzz_byte_slab -- -runs=10000
cd crates/gossip-contracts && cargo +nightly fuzz run fuzz_derivation_chain -- -runs=10000
# gossip-contracts targets
cd crates/gossip-contracts
for target in fuzz_derivation_chain fuzz_item_identity_key; do
echo "Running $target..."
cargo +nightly fuzz run $target -- -runs=1000
done
# gossip-stdx targets
cd ../gossip-stdx
for target in fuzz_byte_slab fuzz_inline_vec fuzz_ring_buffer; do
echo "Running $target..."
cargo +nightly fuzz run $target -- -runs=1000
done
Crashes are saved to fuzz/artifacts/<target>/ within each crate. To reproduce:
cd crates/<crate>
cargo +nightly fuzz run <target> fuzz/artifacts/<target>/<crash-file>
rustup install nightlycargo install cargo-fuzzdevelopment
Deep first-principles code explanation that builds real understanding through phased walkthroughs with diagrams. Covers algorithms, data structures, memory layout, concurrency patterns, and performance tricks — especially for systems code in Rust. Use whenever the user asks to explain, walk through, break down, deep dive into, or understand code. Trigger on "how does this work", "what's happening here", "teach me about this", "why is it done this way", or when the user references a file with @ and wants to understand it. Proactively use when examining code involving lock-free algorithms, atomics/CAS, memory ordering,
development
Use when creating implementation-ready beads tasks that need testing strategy, optimal implementation approach, and documentation requirements baked in — composes /create-task with parallel enrichment agents that analyze the codebase and produce concrete test specifications, algorithm/data-structure guidance, and doc quality standards so implementing agents don't need to re-research
development
--- name: autoresearch description: Autonomous Goal-directed Iteration. Apply Karpathy's autoresearch principles to ANY task. Loops autonomously — modify, verify, keep/discard, repeat. Supports bounded iteration via Iterations: N inline config. version: 1.9.11 --- # Claude Autoresearch — Autonomous Goal-directed Iteration Inspired by [Karpathy's autoresearch](https://github.com/karpathy/autoresearch). Applies constraint-driven autonomous iteration to ANY work — not just ML research. **Core id
development
Use when implementing a new feature and assessing coverage gaps, during periodic test hygiene, when test suites feel bloated, or before merging code that changes coordination or hot paths. Two-phase assess-then-improve testing pipeline.