Couldn't agree more, would love to see this. (Have a horror story about this kind of issue...)
Even though this borders on semantic/symbolic linting, this (use/def checking) is achievable with the style linter. None of the current style lint rules do any symbol tracking/resolution yet, that would be the first step.

b/138353038

There is a somewhat easy way to deal with this.

At the top of a module file, you should set

`default_nettype none

This will cause an undeclared net to trigger a real error in whatever tool the user is using.

A caveat: once you do this, any i/o wire have to be declared explicitly (many people just write input somesig, and that takes advantage of the default nettype being wire).

A 2nd caveat: The default nettype persists across files after a compiler reads it, so you should to set default_nettype back to wire at the end of the file, as a lot of code assumes it.

`default_nettype wire

Now all that said, I would love there to be a lint rule to check if default_nettype is set to none at the start of a file and wire at the end, and that would be a lot easier to implement than trying to verify nets are declared.