dotnet-ci-benchmarking

Compare BenchmarkDotNet results against baselines to detect performance regressions in CI pipelines.

71|10|Updated Feb 11, 2026

Search Tags:#performance #benchmarking #github actions #dotnet #regression testing #CI

Ready to run

npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-ci-benchmarking-wshaddix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-ci-benchmarking
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-ci-benchmarking
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-ci-benchmarking-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents performance regressions from being merged into your codebase by automatically gating your Continuous Integration pipeline based on benchmark results.

Core Features & Use Cases

Automated Threshold Alerts: Set configurable percentage thresholds to automatically detect performance degradations.
Baseline Tracking: Manages baseline performance metrics using BenchmarkDotNet JSON exporters and GitHub Actions artifacts.
Trend Reports: Provides the foundation for tracking performance trends over time.
Use Case: Ensure that new code changes do not negatively impact the performance of critical application paths by automatically failing builds that introduce regressions.

Quick Start

Run the dotnet-ci-benchmarking skill to compare current benchmark results against the baseline with a 10% threshold.

Frequently Asked Questions about dotnet-ci-benchmarking

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

FAQPage Schema

How do I detect .NET performance regressions in GitHub Actions?▼

You can detect .NET performance regressions in GitHub Actions by automating BenchmarkDotNet result comparisons against a tracked baseline, failing the build if results exceed configurable percentage thresholds.

Can I fail a CI build based on BenchmarkDotNet results?▼

Yes, you can fail a CI build based on BenchmarkDotNet results by setting threshold-based alerts that automatically gate the pipeline and prevent merging code that introduces performance degradations.

What is the best way to track benchmark baselines in continuous integration?▼

The best way to track benchmark baselines in continuous integration is by storing BenchmarkDotNet JSON exports as GitHub Actions artifacts, enabling automated comparison and trend reporting for subsequent builds.

Does this performance regression testing approach require specific BenchmarkDotNet versions?▼

Yes, this performance regression testing approach requires BenchmarkDotNet v0.14 or higher to properly export JSON results and integrate with GitHub Actions environments for automated gating.

How do I set a 10% threshold for performance degradation alerts?▼

You can set a 10% threshold for performance degradation alerts by configuring the benchmark comparison logic to automatically fail the build when current results deviate from the baseline by more than 10%.

When should I gate my CI pipeline on benchmark results?▼

You should gate your CI pipeline on benchmark results when you need to ensure new code changes do not negatively impact the performance of critical application paths by automatically preventing regressions from merging.