go-personal-convention

To wrap errors in Go, use fmt.Errorf with the %w verb to preserve the original error while adding a brief description of the failing operation. This ensures logs show exactly which call produced the error during debugging.

The naming convention for boolean variables in Go requires prefixing exported identifiers with Is and unexported identifiers with is. This makes intent explicit and improves readability across service code and struct fields.

To handle enum-like values in Go, define named string types with constant values and store them as TEXT in the database. Prefer human-readable UPPERCASE values to avoid brittle schema migrations and simplify debugging.

Yes, you can review Go source files using this convention by asking the assistant to suggest changes for fmt.Errorf wrapping, Is/is boolean prefixes, and string type enums. It standardizes error context, naming, and limited-value fields.

Yes, Go supports custom string types for fixed-value struct fields. By defining named string types with uppercase constant values, you can represent limited-value fields clearly and store them as TEXT in database models.

Use %w for error wrapping in Go instead of standard formatting to preserve the error chain. Wrapping with fmt.Errorf and %w keeps the original error intact while appending operational context, which simplifies debugging and logging.