Measure what slows delivery

Keep complexity visible before it turns into delivery drag.

SimplicityTools gives .NET teams a clean first run, teach-first diagnostics, and a path from local insight to CI regression gates without forcing a custom process on day one.

Browse docs Install the CLI View GitHub

The first five minutes

dotnet tool install --global SimplicityTools.Cli

dotnet simplicity analyze path/to/YourSolution.sln

dotnet simplicity diff path/to/YourSolution.sln --fail-on-regression

Zero config by default Local first CI-ready

Five surfaces, one contract

The tools reinforce each other. Start with a snapshot, teach the team what matters, then protect the gains instead of letting complexity creep back in.

CLI

Commands that scale from first run to CI

Analyze, baseline, diff, budget, report, and watch all share one simple command surface.

Analyzers

Seven teach-first diagnostics

SF0001-SF0007 make simplification visible in the IDE and build output before code review has to guess.

Filters

Metrics that still tell you what to do next

TwoAmTest, HalfRule, and PrimaryPathFirst turn raw numbers into a conversation teams can actually use.

Reports

Shareable HTML output

Generate a self-contained report when terminal output is not the right artifact for the audience.

Libraries

Programmatic package composition

Use Metrics, Filters, and Tca directly when you want the SimplicityTools contract inside your own tooling.

Adopt it in the order that lowers risk

Do not jump straight to policy. Learn the current shape first, capture the baseline second, then enforce regression only after the team agrees on the contract.

1. Learn the current shape

dotnet simplicity analyze YourSolution.sln

dotnet simplicity budget YourSolution.sln

2. Protect the win

dotnet simplicity baseline YourSolution.sln

dotnet simplicity diff YourSolution.sln --fail-on-regression

Read the guided setup See CI wiring

Diagnostics that teach instead of nag

The analyzer package surfaces structural smells where developers already work. Use it when you want faster feedback than a pull request comment can provide.

Install once

dotnet add package SimplicityTools.Analyzers --prerelease

Keep the reference private

<PackageReference Include="SimplicityTools.Analyzers" Version="x.y.z" PrivateAssets="all" />

Learn the rules

Start with SF0001 and SF0002 if you want the quickest wins from the two available code fixes.

Browse analyzer docs IDE setup Analyzer package

Choose the next page based on the job

Clear internal links matter more than cleverness. Start with the page that matches the decision you are making today.

First run