I highly recommend ShellCheck[0] if you're writing any bash. With the warnings and stylistic advice it provides, I feel like I can actually be confident that my scripts are doing what I think they're doing.
However, don't let it give you a false sense of security.
Shellcheck probably won't say anything about the "biting" parts from the article – because they are valid, just behaving a bit different than the user expects…
That goes for any linter or static analyser i guess.
E.g. "if (x = 1)" is valid C but i'd be pretty unimpressed if a linter didn't flag it up!
Perhaps it's time for a new shell language that is less arcane, with fewer gotchas and simply less bug potential?
Unless you mean something entirely different than POSIX shell family, e.g. Powershell, Python, Ruby, or JS.