I had to dig in a bit to see the whole scope of this project. It seems go-zero has:

1) Go library/main that wraps gRPC handlers to build a server, like Dropwizard or TwitterServer?

2) A CLI tool "goctl" that does code generation for setting up the code layout (server and client API stubs), as well as some Docker/k8s functionality for deploying.

I'm not into Go so can't comment on aspects like the performance benchmark.

However the project documentation is quite interesting if you'd like to see how, presumably the company for which this was built for, their production environment is set up like CI/CD, logging, etc.

It could be more helpful if the architecture diagram showed the roles of the different pieces better. For example it isn't immediately clear what component does authentication so then the JWT can be used for service authorization. So the question would be is how much is the framework tied to some assumptions in a production setup.