golang

To enforce consistent Go coding guidelines, load specific sub-skills for naming, error handling, and concurrency before writing code. This structured approach ensures adherence to best practices and prevents architectural drift across team projects.

The best way to manage context propagation in Go is to pass context as the first parameter and avoid storing it in structs. Following this standard prevents context lifecycle issues and ensures reliable cancellation signals across concurrent operations.

Structuring Go error handling and concurrency rules involves selectively loading modular sub-skills before code creation. This provides actionable checklists and specific guidelines, ensuring standardized outcomes for complex concurrent processes.

Yes, you need to apply gofmt formatting before writing Go code. Applying gofmt standardizes syntax formatting, ensuring that all generated code complies with baseline style requirements and reduces unnecessary review friction.

Yes, you can use these Go coding standards for automated code reviews. The centralized guidelines and modular rule checklists support faster onboarding and provide clear, actionable criteria for validating code modifications.

Go code suffers from architectural drift during modifications when inconsistent styles are applied without structured guidelines. Loading applicable sub-skills before editing enforces standardized error handling and naming conventions, preventing brittle code.