LowFile-scopeJava Plug & play

Maintain Consistent Annotation Placement

Ensure that annotations are placed consistently before or after modifiers throughout the codebase.

Why this matters

Inconsistent annotation placement (before or after modifiers) reduces readability and can cause confusion when following coding conventions.

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

Avoid

@Override public void someMethod() { ... }

Prefer

@Override
public void someMethod() { ... }

Bad

@Override public void someMethod() { ... }

Good

@Override
public void someMethod() { ... }

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