eng-code-guidelines
FeaturedGo production discipline for Compozy. Use when writing or editing non-test Go files under cmd or internal, including config, logging, CLI, concurrency, and process-lifecycle paths. Do not use for Go tests; pair it with the narrower schema, contract, or cleanup skill when those domains apply.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- compozy
- Repository
- compozy/compozy
- Created
- 7 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
eng-test-conventions
Go test-shape discipline for Compozy. Use when writing or editing *_test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.
go-code-style
Go coding conventions that follow established industry standards: Effective Go, the Go wiki's Code Review Comments, the Go Doc Comments guide, and the Google Go Style Guide (guide, decisions and best practices). Covers tooling, formatting, naming, packages and imports, errors, panics, declarations, control flow, functions, receivers, interfaces, generics, contexts, concurrency, global state, logging and doc comments. TRIGGER when: writing, editing, formatting, or reviewing Go code (.go files), or asked to "fix style" / "check code quality" in a Go project. DO NOT TRIGGER when: working in a non-Go language, or only reading code without making changes.
go-conventions
Go code conventions covering Effective Go, error wrapping, golangci-lint, govulncheck, table-driven tests, interfaces, context usage, modules, and concurrency. Load when writing or reviewing Go code.