Tools as dependencies
This example is a slight tweak on the best-practices example for working with Go modules as development dependencies.
The downside of the existing example is that someone who
git clones your module to make a contribution, would not be able to run
go generate (without extra work).
$ go generate painkiller.go:5: running "stringer": exec: "stringer": executable file not found in $PATH