Menu
Run Criterion benchmarks with baseline comparison for performance optimization work
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/ahrav/scratch-scanner-rs --skill bench-compareThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Write-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.
Showing SKILL.md
| name | bench-compare |
| description | Run Criterion benchmarks with baseline comparison for performance optimization work |
Compare benchmark results against a baseline to measure optimization impact.
Invoke with optional benchmark filter:
bench-compare - Run all benchmarksbench-compare scan - Run only scan-related benchmarksbench-compare throughput - Run throughput benchmarksBefore making changes, save current benchmark results:
cargo bench --bench <name> -- --save-baseline before
Or for all benchmarks:
cargo bench -- --save-baseline before
Make the optimization changes to the codebase.
Run benchmarks against the saved baseline:
cargo bench --bench <name> -- --baseline before
Look for these patterns in Criterion output:
Performance has improved - Optimization successfulPerformance has regressed - Changes hurt performanceNo change in performance - Within noise thresholdProvide a summary table:
| Benchmark | Before | After | Change |
|---|---|---|---|
| name | X ns | Y ns | -Z% |
The project has these benchmark files in :
benches/scan.rs - Core scanning performancescanner_throughput.rs - End-to-end throughputvectorscan_overhead.rs - Vectorscan integration overheadrule_isolation.rs - Per-rule cost isolationhotspots.rs - Known hot path benchmarks (requires bench feature)validator.rs - Validation step benchmarks (requires bench feature)ring_buffer, fixed_set, fixed_vec, timing_wheel, etc.--bench <name> to run specific benchmarks for faster iterationhotspots and validator benches require: cargo bench --features benchmemory_bandwidth.rs