LowFile-scopeRuby Plug & play

Use `CamelCase` for Class and Module Names

Check if class and module titles use CamelCase. If not, suggest renaming them for consistency.

Why this matters

Classes and modules in Ruby should follow CamelCase naming conventions, making them easily distinguishable and improving code organization.

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

Avoid

class myclass
end

Prefer

class MyClass
end

From the same buckets as this rule.

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
Prefer `str.replace()` Over `re.sub()` for Simple Cases
Detect uses of `re.sub()` where regular expressions are not needed. For simple string replacements, `str.replace()` is more efficient and should be used instead.
performance-efficiencystack-python+1
Critical
Use Factory Method Injection in `@Configuration` Classes
Ensure that factory method injection is used in `@Configuration` classes instead of `@Autowired` field injection.
module-architecturestyle-conventions