fibgen generates a complete OpenAPI 3.1 / 3.0 spec for Go Fiber services — with zero annotations. No @Summary comments, no codegen, no changes to your handlers. Point it at your project and get paths, params, request bodies, per-status responses, and resolved type schemas ($ref, enums, nullables). Fiber handlers are opaque at runtime, so fibgen reads the code itself via go/types, recovering types from your c.Bind() and c.JSON() calls. Fiber v2 & v3. Open source, MIT

Hey Product Hunt 👋 I built fibgen because keeping Swagger annotations in sync with handler code is a chore — and they rot the moment someone forgets a comment. I wanted docs that come from the actual code, not a parallel description of it. The hard part: Fiber handlers are completely opaque at the type level (func(c fiber.Ctx) error), so there's nothing to reflect on at runtime. fibgen does real static analysis — it walks the route registrations, resolves group prefixes through variables, enters the handler body, and pulls types out of the c.* calls. Would love feedback on which patterns it should learn next — interprocedural analysis (following respondJSON(c, user) helpers) is top of my list. What would make this a daily driver for you?

Fibgen

Auto-generate OpenAPI docs from Go Fiber code — no comments

Auto-generate OpenAPI docs from Go Fiber code — no comments