surface-benchmarker

Run and interpret Hex1b Surface API benchmarks with BenchmarkDotNet and dotnet run.

173|17|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/mitchdenny/hex1b --skill surface-benchmarker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: surface-benchmarker
Source: https://github.com/mitchdenny/hex1b/tree/main/.github/skills/surface-benchmarker
Command: npx skills add https://github.com/mitchdenny/hex1b --skill surface-benchmarker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams benchmark the Hex1b Surface API to detect performance regressions after making changes to the Surface code paths.

Core Features & Use Cases

  • Benchmark planning: Identify critical surface paths to benchmark (CreateSurface, WriteText, Diff, Tokens) and define representative workloads.
  • Result interpretation: Analyze mean/median timings and memory allocations to guide optimization decisions.
  • CI integration: Integrate benchmarks into CI to automatically flag regressions when code changes are merged.

Quick Start

Use the Quick Reference in the SKILL.md to run the Surface benchmarks with the BenchmarkDotNet-based project and dotnet run commands.

Frequently Asked Questions about surface-benchmarker

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

FAQPage Schema
How do I benchmark Surface API code paths after making changes?

To benchmark Surface API performance, use BenchmarkDotNet with dotnet run commands to measure core operations like CreateSurface, WriteText, Diff, and Tokens. The skill provides a Quick Reference for executing these benchmarks during development.

What is performance regression detection for Surface API operations?

Performance regression detection for Surface API operations involves running benchmarks on modified code under src/Hex1b/Surfaces/ to verify changes do not degrade performance. It analyzes mean and median timings alongside memory allocations to identify regressions in core surface operations.

Can I integrate BenchmarkDotNet benchmarks into CI workflows for Surface API changes?

Yes, you can integrate BenchmarkDotNet benchmarks into CI workflows to automatically flag performance regressions when Surface API code changes are merged. The skill encapsulates guidance on which tooling commands to use for both development and CI pipeline integration.

How do I interpret Surface API benchmark results for optimization decisions?

To interpret Surface API benchmark results, analyze mean and median timings alongside memory allocations to guide optimization decisions. The skill provides guidance on reading BenchmarkDotNet output to determine whether changes to surface operations introduce performance regressions.

Which Surface API operations should I benchmark to detect performance regressions?

You should benchmark critical surface paths including CreateSurface, WriteText, Diff, and Tokens to detect performance regressions. The skill helps identify these representative workloads and defines which core surface operations require benchmarking after code modifications.