What problem does it solve? Go APIs often ship without accurate OpenAPI documentation, or their Swagger specs drift out of sync with the actual handlers. This Skill guides the creation and auditing of swaggo/swag annotation comments so the generated Swagger UI stays a correct, complete contract for API consumers. ## Core Features & Use Cases - Build mode: Set up the swag toolchain, annotate handlers with @Summary, @Param, @Success, @Router, and @Security, run swag init, and wire the Swagger UI endpoint for Gin, Echo, Fiber, Chi, or net/http. - Audit mode: Review existing annotations for completeness, correctness, and security coverage, catching common mistakes like missing docs imports, stale generated specs, or unprotected routes lacking @Security. - Struct enrichment: Apply struct tags such as swaggertype, enums, example, minimum/maximum, and swaggerignore so generated schemas reflect real types like time.Time and []byte. - Use Case: You inherit a Gin service with no API docs. The Skill walks you through adding general API info in main.go, annotating each handler, defining Bearer JWT security, running swag init, and serving the UI at /swagger/index.html. ## Quick Start Ask the agent to add Swagger annotations to your Go handlers and generate the docs with swag init, then wire the Swagger UI route for your framework.
