bench

Execute a metric command N times across 2-3 repo variants and emit markdown and TSV reports.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill bench-arbazkhan971
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bench
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/bench
Command: npx skills add https://github.com/arbazkhan971/godmode --skill bench-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates statistically valid performance comparisons by executing a user-provided metric command N times across 2-3 repo variants and reporting reproducible results.

Core Features & Use Cases

  • Automates N-run benchmarking across 2-3 code states (variants) to quantify performance changes.
  • Computes mean, median, standard deviation, and delta against a named baseline using awk (no external deps).
  • Outputs a tabular markdown report and a dedicated TSV file with per-variant metrics and a one-paragraph summary.
  • Enforces a clean git workspace, snapshots and restores the starting state, and performs variance recovery with up to three retries.
  • Suitable for evaluating performance regressions, feature branches, and architecture changes.

Quick Start

Run /godmode:bench with a metric_cmd and 2-3 variants to compare their performance.

Frequently Asked Questions about bench

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate performance benchmarking across different git branches?▼

Automate performance benchmarking across git branches by executing a user-provided metric command N times across 2-3 repo variants. The process snapshots and restores your git workspace, runs the benchmarks, and calculates delta percentages to quantify performance changes.

How do I compare code performance variants and calculate percentage deltas?▼

Compare code performance variants by running a metric command N times across 2-3 states and calculating delta percentages using awk. The process enforces N>=3 runs and performs variance recovery with up to three retries to ensure reproducible results.

Can I benchmark code changes safely without messing up my git workspace state?▼

Yes, you can benchmark code changes safely because the process enforces a clean git workspace, automatically snapshots your starting state, and restores it after executing the performance comparisons across the specified variants.

How are performance benchmarking results reported and exported?▼

Performance benchmarking results are reported and exported by emitting a tabular markdown report and a dedicated TSV file. These outputs include per-variant metrics like mean, median, and standard deviation, alongside a one-paragraph summary.

What is statistically valid variance recovery in code benchmarking?▼

Statistically valid variance recovery in code benchmarking is a mechanism that enforces a minimum of three runs and performs up to three retry attempts. This ensures the collected performance metrics are reproducible and statistically reliable.