Defines Go request and response structs with validate, from, and JSON tags for OpenAPI emission.
npx skills add https://github.com/gabriellst/codm --skill schema-go-gabriellst
Please help me install this Agent Skill. Skill: schema-go Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/schema/go Command: npx skills add https://github.com/gabriellst/codm --skill schema-go-gabriellst
validate:"..." tags consumed by go-playground/validator/v10, with from:"body|param|query|header|cookie" tags controlling how httputil.DecodeRequest binds values. - Output struct conventions: Standard json tags plus example and format tags drive the build-time OpenAPI 3.1 emitter, with pointer fields becoming nullable schemas. - OpenAPI metadata wiring: Controller Metadata() methods reference zero values of request and response structs so the emitter discovers schemas, and swaggerignore:"true" hides infrastructure fields like owner IDs. - Use Case: When adding a new endpoint such as a transcoder callback webhook, define the request struct with from/validate tags in the controller file, reuse the use case output struct as the response, and list domain error codes in Metadata so the generated OpenAPI spec stays accurate. ## Quick Start Ask the agent to define the input and output structs for a new Go endpoint following the schema-go conventions, including validate tags, from tags, and Metadata wiring.High-intent search queries and answers about installing and using this skill.
Add a validate tag to every field, such as validate:"required,uuid" or validate:"omitempty,min=1,max=100" for optional fields. The validator runs after httputil.DecodeRequest populates the struct, and failures return an AppError with code CodeValidationFailed and HTTP 422.
Use from tags on controller request structs: from:"query", from:"header", from:"param", from:"body", or from:"cookie". httputil.DecodeRequest reads these tags and coerces string values to int, bool, or float64 as needed before validation.
Add swaggerignore:"true" to fields that consumers should not see, such as an owner ID read from a session header. The reflection-based emitter in packages/api/go/core/pkg/openapi excludes these fields from the generated OpenAPI 3.1 schema.
No. Define input and output structs in the same file as the use case or controller that owns them. Reuse the use case output struct directly as the controller response in Metadata to avoid duplication and keep the emitter contract consistent.
The field likely carries swaggerignore:"true", or the controller Metadata does not reference the struct as a zero value in Request or Response. The emitter only discovers schemas through Metadata and skips swaggerignore fields by design.
jmdueaMap domain concepts to Rust structs, enums, and traits.
LuminaVaultGenerates OpenAPI/Swagger documentation for Go APIs using swaggo/swag annotations.
lushly-devGenerate OpenAPI, TypeScript, and Python Pydantic models from TypeSpec definitions.
kubb-labsImport and use Kubb-generated types, clients, hooks, schemas, and mocks in application code.