go-backend

name	go-backend
description	System Bridge Go backend conventions - error wrapping, graceful degradation for data modules, nil-pointer safety, context-aware Module.Update, structured slog logging, and errcheck-clean deferred cleanup. Use when writing or reviewing Go code in the system-bridge backend (data modules, HTTP/WebSocket APIs, CLI, discovery).

System Bridge Go Backend

Project-specific Go patterns for the system-bridge backend. General Go style an agent already knows is intentionally omitted.

Format and Lint

• Always run go fmt ./... from the repo root after editing Go.
• Before committing, run mise run lint:all (or golangci-lint run ./...).
• CI runs golangci-lint. Watch errcheck: never leave unchecked error returns, especially deferred cleanup. All deferred os.RemoveAll() calls in tests must check the error.

File Naming

• Go files lowercase.go, tests _test.go.
• OS-specific files use build-tag suffixes: module_linux.go, module_windows.go, module_darwin.go.
• Avoid generic names like utils.go; be specific.

Error Handling

// Wrap errors with context
if err != nil {
    return cpuData, fmt.Errorf("error getting CPU count: %v", err)
}

// Handle at the appropriate level; degrade gracefully only where safe
data, err := getData()
if err != nil {
    slog.Error(, , err)
     defaultData, 
}