LowFile-scopeKotlin Plug & play

Rename functions to reflect their purpose

Function names must describe side effects and return values (e.g., fetchUser vs. process).

Why this matters

Improves discoverability and reduces misuses.

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

Avoid

fun process(u: String) = http.get(u)

Prefer

fun fetchUser(userId: String): User = api.getUser(userId)

Bad

doStuff()

Good

calculateChecksum()

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