go-code-style

To enforce idiomatic Go coding standards during a refactor, consult the references/go-standards.md file and align code with go.mod, package naming, error handling, and documentation guidelines. This ensures new and existing code follows repository conventions.

The best way to review Go code for project-specific error handling and formatting rules is to run an automated review pass against the target package. This checks the code against idiomatic Go practices and repository standards outlined in the project references.

Yes, you can align API surface designs with existing Go module paths. The process respects the repository's go.mod file for versioning and module path configuration, ensuring that API refactoring matches the declared module structure and package names.

Writing Go tests requires consulting the repository's coding standards reference to ensure idiomatic practices. The reference file specifies error handling, formatting, and documentation guidelines that apply equally to test code and feature implementations.

A Go package refactor fails to meet project standards when it ignores specific repository references. General Go conventions are insufficient; you must ensure the target package name matches exactly and follow the guidelines specified in references/go-standards.md.