Menu
SkillsMP has collected 6 skills from DRMacIver/hegel-rust-oss-bug-finding. Open a skill to review its source and details.
Showing 6 of 6 collected skills.
Property-test a storage engine's crash/power-loss recovery by injecting simulated crashes through its storage-backend abstraction: a backend that separates "written" from "fsynced" bytes, plus a full write log that lets you cut the stream anywhere (including…
Build a stateful, model-based property test for a stateful Rust API (a data structure, store, engine, or VM) with hegel — drive a random sequence of operations against both the real system and a simpler reference model, and assert equivalence plus invariants…
Close the last uncovered regions of a dependency under property test by measuring per-file region coverage of the DEPENDENCY (not your crate), reading why each cold region is cold, and writing property-shaped tests — with a real oracle, not mere calls — that…
Property-test a stateful Rust API without a reference model, using hegel: metamorphic relations (two executions whose results must relate in a known way — commuting operations, do/undo identities, batch-equals-loop, reset-equals-fresh) and differential…
Decide whether a bug found in someone else's crate is actually worth reporting, and how strong a finding it is, before writing it up. Use when triaging a candidate bug, selecting which findings to file upstream, or sanity-checking a severity claim. Guards…
Write an upstream bug report or GitHub issue draft for a bug found in someone else's project. Use when drafting bug reports, issue text, or reproductions to send to a crate's or library's maintainers. Produces a short, plainly-written report led by a runnable…