Edge Case Handling
Detects potential null dereferences and missing validation in added code.
Why this rule exists
Most production NullReferenceExceptions come from added code that assumes non-null inputs without guarding for them. The cost of one guard clause is a few characters; the cost of a missing one is a 2 a.m. page.
Code example
+ public string FormatName(User user) => user.FirstName + " " + user.LastName;+ public string FormatName(User user)
+ {
+ ArgumentNullException.ThrowIfNull(user);
+ return $"{user.FirstName} {user.LastName}";
+ }Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0006": { "enabled": true, "severity": "Warn" }
}
}See Configuration for the full schema.
Related rules
Behavioral Change Detection
Detects removed logic lines and changed method signatures that alter runtime behavior without corresponding test updates.
Nullability and Type Safety
Detects null-forgiving operator (!) overuse, pragma warning disables for nullable, and unchecked as-casts that bypass the type system.
Error Handling Integrity
Detects swallowed exceptions (empty catch blocks) and exception handling patterns that hide failures from callers and operators.
Discussed in
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0006_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.