A comparison with other fasthttp-based frameworks like https://github.com/savsgio/atreugo or https://github.com/gofiber/fiber would also be interesting.
Or maybe a benchmark along the lines of https://github.com/smallnest/go-web-framework-benchmark.
Looking at the commit history (7 commits, most of them from yesterday), the open issues (no way to define URL path variables yet, https://github.com/abahmed/gearbox/issues/15), and the release being v0.0.1, maybe it's a bit too early for a ShowHN?
But if you have a vision of how it will be different and better than existing frameworks and the willingness to keep working on your project, then honestly good luck with it, it might become interesting in the future!
This is why we have so much crap on GitHub. OP has admitted this solves no real-world problems, and I would argue there is nothing wrong with net/http that it would require anyone to bother installing this stuff.
If it's not production-ready, who are these micro services for?
It just seems not even close to polished enough to share it with the wider community. Someone may take this at face-value and try and use it for their own purposes, only to discover it's a purely academic pursuit with no actual merits other than 'oh we might be able to spuriously improve performance.'
I think other commenters have got it right in saying that processing requests is _not_ the bottleneck of most micro services, but interaction with a storage layer or network speed.