code-style-and-conventions

Enforce consistent code style across Go and TypeScript by applying gofmt, strict TypeScript guidance, and unified naming rules. This ensures cross-language consistency and reduces maintenance friction as the codebase grows.

A pull request review checklist for error handling and logging should require explicit error handling, safe logging that avoids secret leakage, and correct context propagation with timeouts for external calls to ensure reliability.

Yes, this code style standard works with React, TypeScript, Go, and structured documentation formats like JSON, YAML, and Markdown. It applies consistent naming and formatting conventions across all these file types.

Validate AI-assisted code generation by using checklist-driven standards for code style, quality gates, and safe implementation practices. This verifies that generated code meets explicit error handling, test coverage, and formatting requirements.

Structure test coverage to satisfy quality checks by writing tests that explicitly cover both happy and error paths. This guarantees reliability-focused engineering and validates safe async or streaming behavior during failures.