Tooling
CLI Tool
Analyze, document, and benchmark your TurboMediator setup
The dotnet-turbo CLI tool provides analysis, documentation generation, health monitoring, and benchmarking capabilities.
Installation
dotnet tool install --global TurboMediator.CliCommands
analyze — Handler Coverage
Analyzes your project for handler coverage, identifying missing or duplicate handlers:
dotnet-turbo analyze -p ./src/MyAppOutput:
📊 TurboMediator Analysis
─────────────────────────
Messages found: 15
Handlers found: 14
✅ CreateUserCommand → CreateUserHandler
✅ GetUserQuery → GetUserHandler
✅ UserCreatedNotification → EmailHandler, LogHandler
⚠️ OrphanedCommand → No handler found!
Coverage: 93% (14/15)docs — Generate Documentation
Generates API documentation from your codebase in markdown, HTML, or JSON format:
# Markdown (default)
dotnet-turbo docs -p ./src/MyApp -o ./docs -f markdown
# HTML
dotnet-turbo docs -p ./src/MyApp -o ./docs/api -f html
# JSON (for programmatic use)
dotnet-turbo docs -p ./src/MyApp -o ./api-docs.json -f jsonGenerated documentation includes:
- All message types with their properties
- All handlers with their associated messages
- Pipeline behaviors and their order
- XML doc comments (if present)
health — Health Check
Check the health of a running TurboMediator application:
# One-time check
dotnet-turbo health -e https://localhost:5001/health
# Watch mode with live table
dotnet-turbo health -e https://localhost:5001/health --watchWatch mode displays a live Spectre.Console table that auto-refreshes.
benchmark — Performance Analysis
Analyzes handler complexity and estimates performance characteristics:
dotnet-turbo benchmark -p ./src/MyAppOutput:
🚀 TurboMediator Benchmarks
───────────────────────────
Handler Analysis:
CreateUserHandler
Complexity: Medium
Async Operations: 2 (DB write, notification publish)
Estimated Latency: 5-15ms
GetUserHandler
Complexity: Low
Async Operations: 1 (DB read)
Estimated Latency: 1-5ms
ProcessVideoHandler
Complexity: High
Async Operations: 4 (API call, S3 upload, DB write, notification)
Estimated Latency: 100-500msThe CLI tool uses MSBuild/Roslyn workspace to analyze your source code at the syntax and semantic level. It doesn't require compiling or running your application.