How do I install GauntletCI?

Install GauntletCI as a .NET global tool: dotnet tool install -g GauntletCI. Requires .NET 8 or later.

How do I run my first analysis?

Run gauntletci analyze --staged to analyze staged changes before committing. You can also pipe a diff from stdin with git diff HEAD | gauntletci analyze, or point at a saved diff file with gauntletci analyze --diff changes.diff.

How do I install GauntletCI as a pre-commit hook?

Run gauntletci init inside your repository. The hook runs gauntletci analyze --staged automatically before every commit and blocks the commit with exit code 1 if blocking findings are detected.

Does GauntletCI require a cloud connection?

No. GauntletCI runs entirely on your local machine. All analysis is local and deterministic. No code or diff content is sent to any external service.

What does GauntletCI analyze?

GauntletCI reads the exact lines added and removed in your diff and evaluates them against 37 deterministic rules. It flags behavior changes without test updates, breaking API changes, new exception paths, removed null guards, and hardcoded secrets.

Documentation

Getting Started

GauntletCI is a local-first change risk engine for C# and .NET. It analyzes pull request diffs to catch breaking changes and regressions before they merge, with no cloud connection required.

Install

.NET global tool (all platforms)

$ dotnet tool install -g GauntletCI

Requires .NET 8 or later. Updates with dotnet tool update -g GauntletCI.

Windows (winget)

PS> winget install EricCogen.GauntletCI

macOS / Linux (Homebrew)

$ brew tap EricCogen/gauntletci

$ brew install gauntletci

Manual (self-contained binary)

Download a self-contained binary from the latest GitHub release. No .NET installation required. Available for win-x64, win-arm64, osx-x64, osx-arm64, linux-x64, and linux-arm64.

Run your first analysis

$ gauntletci analyze --staged

# Analyze your staged changes before committing

$ gauntletci analyze --diff pr.diff

# Analyze a saved diff file

$ git diff HEAD | gauntletci analyze

# Pipe a diff from stdin

Install as a pre-commit hook

Run this once inside your repository. GauntletCI will analyze your staged diff automatically before every commit.

$ gauntletci init

The hook runs gauntletci analyze --staged and exits with code 1 if findings are detected, blocking the commit.

What it analyzes

GauntletCI reads the exact lines added and removed in your diff and evaluates them against 37 deterministic rules. It flags:

+Behavior changes without corresponding test updates
+Breaking public API or method signature changes
+New exception paths with no callers prepared to handle them
+Removed null guards or defensive checks
+Implicit dependency behavior shifts
+Hardcoded secrets and SQL injection risks

What it is not

GauntletCI is not a linter, formatter, test runner, or full-codebase static analysis replacement. It focuses on one question: did this diff introduce behavior that is no longer properly validated?

It runs alongside your existing tools; it does not replace them.

Next steps

Live Demo

Inspect real scenario PRs and GitHub Actions checks

Privacy Modes

Default, Local AI, Integration, CI AI

CLI Reference

All commands and flags

Rule Library

All detection rules

Configuration

.gauntletci.json reference

CI/CD Integrations

GitHub Actions and more

Pricing

Free during beta - see licensing details