split-asm

Split BenchmarkDotNet assembly markdown files into per-method files.

604|41|Updated Jun 11, 2020
One-click install
npx skills add https://github.com/bitfaster/BitFaster.Caching --skill split-asm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-asm
Source: https://github.com/bitfaster/BitFaster.Caching/tree/main/.claude/skills/split-asm
Command: npx skills add https://github.com/bitfaster/BitFaster.Caching --skill split-asm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill splits a monolithic BenchmarkDotNet assembly markdown file into individual per-method files, enabling granular diffs, easier navigation, and clearer review workflows.

Core Features & Use Cases

  • Per-method file generation from a single BenchmarkDotNet markdown document.
  • Hierarchical organization by target benchmark, then framework for straightforward exploration.
  • Enables diffs and reviews at the method level within existing benchmarking workflows.

Quick Start

Run the splitasm tool to break down a BenchmarkDotNet assembly markdown file into separate files for each benchmark method. This enables using file diffs to compare code changes across methods.

  • Example: dotnet run --project C:/repo/splitasm/splitasm -- <ResultsPath>
  • If no path is specified, default to the standard BenchmarkDotNet output location: dotnet run --project C:/repo/splitasm/splitasm -- BenchmarkDotNet.Artifacts/results

Frequently Asked Questions about split-asm

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

FAQPage Schema
How do I split BenchmarkDotNet markdown results into separate files for each method?

To split BenchmarkDotNet markdown results, run the splitasm tool via the .NET toolchain to read the monolithic assembly markdown and generate individual per-method files. This organizes outputs hierarchically by target benchmark and framework for granular diffs.

What is the best way to diff per-method benchmark results in BenchmarkDotNet markdown?

The best way to diff per-method benchmark results is to split the monolithic BenchmarkDotNet markdown file into individual files. This enables file diffs to compare code changes across methods clearly within existing benchmarking workflows.

Does splitasm require a specific path to locate BenchmarkDotNet output files?

Splitasm does not require a specific path; if no path is specified, it defaults to the standard BenchmarkDotNet output location at BenchmarkDotNet.Artifacts/results to read and process the markdown input.

Can I use the splitasm tool to organize benchmark outputs by framework and target?

Yes, you can use the splitasm tool to organize benchmark outputs. It reads BenchmarkDotNet markdown and structures the generated per-method files hierarchically by target benchmark, then by framework for straightforward exploration.

Why do I need to split BenchmarkDotNet assembly markdown files?

You need to split BenchmarkDotNet assembly markdown files to enable granular diffs, easier navigation, and clearer review workflows. Breaking down the monolithic document into per-method units allows precise method-level comparison of code changes.

Do I need the .NET toolchain installed to split BenchmarkDotNet markdown files?

Yes, you need the .NET toolchain installed to split BenchmarkDotNet markdown files. The splitasm project relies on .NET to run the tool via dotnet run --project commands to parse and generate the per-method output structure.