LowFile-scopeC# Plug & play

Refactor large methods into smaller functions

Split long methods into cohesive private helpers with clear names and single responsibilities.

Why this matters

Improves readability, testability, and reduces bug surface.

Side-by-side examples engineers can pattern-match during review.

Avoid

public void Process(){ /* 200+ lines */ }

Prefer

public void Process(){ Validate(); var data = Load(); var result = Transform(data); Save(result); }

Bad

void Big(){ /* ...long... */ }

Good

void Big(){ Step1(); Step2(); Step3(); }

From the same buckets as this rule.

Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid equality operators in loop termination conditions
Check if loops use equality operators (== or !=) in termination conditions. These can lead to infinite loops if the condition is never met exactly. Instead, use relational operators like < or > for safer loop termination.
error-handlingreadability-refactor
Critical
Avoid Equality Operators in Loop Termination Conditions
Ensure that relational operators (`<`, `>`) are used instead of equality operators (`==`, `!=`) in loop termination conditions.
readability-refactor