LowFile-scopeJava Plug & play

Declare Variables Near Their First Use

Ensure that variables are declared as close as possible to their first use to improve readability.

Why this matters

Declaring variables far from their usage reduces clarity and makes it harder to track their purpose, leading to maintainability issues.

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

Avoid

int result;
// Many lines of code
result = computeResult();

Prefer

int result = computeResult();

Bad

int result;
// Many lines of code
result = computeResult();

Good

int result = computeResult();

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