HighFile-scopeRuby Plug & play

Specify StandardError explicitly in rescue blocks

Avoid bare `rescue`; rescue StandardError (or a narrower class) and log with context.

Why this matters

Prevents accidentally catching system-level exceptions and improves observability.

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

Avoid

begin
  risky
rescue
  # swallowed
end

Prefer

begin
  risky
rescue StandardError => e
  Rails.logger.error("risky failed", error: e)
  raise
end

Bad

rescue; end

Good

rescue StandardError => e; log; raise

From the same buckets as this rule.

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 Returning Null in Non-Async Task Methods
Returning null from a Task or Task<T> method causes a NullReferenceException if awaited. Use Task.CompletedTask or Task.FromResult<T>(null) instead.
error-handlingreadability-refactor+1
Critical
Avoid Using Boolean Expressions in `except` Statements
Detect `except` clauses that use `or` or `and` to catch multiple exceptions. This does not work as intended. Recommend using a tuple of exceptions instead.
error-handlingstack-python