Proactively searching for these anti-patterns is hard enough. Doing something about it before it explodes is even harder. This is why I like community driven problem detection. You can leverage their experience on top of yours to help make the case for action.
Days ago, I detected a query in a system in development that immediately triggered an alert on me.
I communicated this finding to the team but wasn't firm enough to force an immediate change or fix it.
I deeply regret it. This is what happened later:
When multiple users tested the App concurrently, the database collapsed and everybody went desperate looking for the cause.
This reminds me of a rule:
Do not delay any fix to your database design or queries.
If you see a query "smelling" bad, believe me, it will transform your whole application into a real piece of shit.