Comment 1:

The correct incantation is "go tool vet -h". This is cryptic, I agree.
The flags printed by "go tool vet -h" are only accessible via "go tool vet".
I'll try adding some language

Status changed to adg.

Comment 2:

... to clarify the usage message a bit.

Labels changed: added documentation.

Owner changed to @adg.

Status changed to Accepted.

Comment 3:

Did you notice this message?
> To run the vet tool with specific options, run 'go tool vet'.
If you follow the instruction, here's what happens:
$ go tool vet
Usage of vet:
    vet [flags] directory...
    vet [flags] files... # Must be a single package
  -all=true: check everything; disabled if any explicit check is requested
  -asmdecl=false: check assembly against Go declarations
  -assign=false: check for useless assignments
  -atomic=false: check for common mistaken usages of the sync/atomic package
  -buildtags=false: check that +build tags are valid
  -composites=false: check that composite literals used field-keyed elements
  -compositewhitelist=true: use composite white list; for testing only
  -copylocks=false: check that locks are not passed by value
  -methods=false: check that canonically named methods are canonically defined
  -nilfunc=false: check for comparisons between functions and nil
  -printf=false: check printf-like invocations
  -printfuncs="": comma-separated list of print function names to check
  -rangeloops=false: check that range loop variables are used correctly
  -shadow=false: check for shadowed variables (experimental; must be set explicitly)
  -shadowstrict=false: whether to be strict about shadowing; can be noisy
  -structtags=false: check that struct field tags have canonical format
  -test=false: for testing only: sets -all and -shadow
  -unreachable=false: check for unreachable code
  -v=false: verbose
Isn't that what you were looking for?

Status changed to WaitingForReply.

Comment 4:

Yes, that's it. I guess the message didn't really clue me in to it. The distinction
between running "go vet" and "go tool vet" is subtle enough that I must have glossed
over it, but I don't see any easy way that can be improved short of increasing my
reading comprehension :)
The part that says > For more about vet, see 'godoc code.google.com/p/go.tools/cmd/vet'.
still leads to outdated documentation though.

Comment 5:

Wow, yeah, that's pretty out of date. Sent a CL:
https://golang.org/cl/61480044

Status changed to Started.

Comment 6:

This issue was closed by revision golang/tools@47596b4.

Status changed to Fixed.