golang-swagger

To generate OpenAPI docs from Go code, you annotate HTTP handlers using swaggo/swag syntax like @Summary, @Param, and @Router, then run swag init to produce the spec. This Skill guides annotation syntax and swag init execution for accurate API contracts.

You wire Swagger UI into Go HTTP frameworks by registering the generated spec endpoint at /swagger/index.html. This Skill provides middleware integration for Gin, Echo, Fiber, Chi, and net/http to serve the interactive UI.

Yes, you can define JWT, Bearer, OAuth2, API key, and basic auth security schemes in swaggo/swag using the @Security annotation. This Skill helps configure security definitions for protected API operations.

You handle complex Go types in Swagger documentation by using struct tags like swaggertype, swaggerignore, and example to override schema generation. This Skill ensures correct schemas for tricky Go types and enums.

Yes, this Swagger generation approach works with Gin, Echo, Fiber, Chi, and net/http. The Skill provides framework-specific middleware integration to register the Swagger UI endpoint across these popular Go HTTP routers.

Swagger annotations may not show up if swag init fails or annotation syntax is inconsistent across operations, parameters, and responses. This Skill enforces consistent annotation syntax and proper struct tag usage to resolve missing docs.