Generate OpenAPI specifications from Go swaggo annotations.
npx skills add https://github.com/333-333-333/agents --skill go-api-docs
Please help me install this Agent Skill. Skill: go-api-docs Source: https://github.com/333-333-333/agents/tree/main/skills/go-api-docs Command: npx skills add https://github.com/333-333-333/agents --skill go-api-docs
Efficiently derive OpenAPI specifications and service-level README conventions from Go code annotations, keeping API docs accurate with minimal manual editing.
Run swag to generate OpenAPI docs from your Go code and review them in the docs directory.
High-intent search queries and answers about installing and using this skill.
You can generate OpenAPI documentation from Go code by applying swaggo annotations to your handlers and models, then running swag to output swagger.json specifications into your docs directory.
To keep Swagger specs synced with API changes in CI, configure your pipeline to run swag and regenerate the OpenAPI specifications whenever Go microservice code is updated, ensuring docs never drift.
Yes, this approach works for individual Go microservices by maintaining a separate docs/swagger.json and README template per service, keeping each service's API documentation isolated and accurate.
The best way to maintain per-service API docs without manual editing is deriving OpenAPI specifications directly from Go swaggo annotations, keeping READMEs and Swagger specs automatically consistent with code.
Swaggo annotations might not appear in Swagger UI if they are incorrectly formatted or placed outside the handler function, preventing swag from parsing your Go code into OpenAPI specifications.
constzzGenerate Swagger/OpenAPI documentation for Go projects from code annotations.
giuseppe-trisciuoglioGenerate OpenAPI 3.0 documentation and Swagger UI for Spring Boot 3.x applications.
dashkanGenerate Swagger/OpenAPI documentation from Go code using swaggo annotations.
juburrGenerate Go protobuf code from proto3 schemas for gRPC services.
