go-style

To standardize Go code style, apply shared conventions for pointer initialization, import aliasing, logger naming, and test structure so code stays grepable and aligned with existing package patterns. This consistency reduces review churn and style drift across repositories.

For pointer-field initialization in Go refactoring, use direct new(value) initialization instead of creating temporary locals. This approach keeps code cleaner and produces more consistent diffs when rewriting services to match established repository conventions.

Yes, these Go style conventions require keeping imports unaliased by default and naming slog loggers logger for clarity. Adhering to these shared repository conventions ensures code stays consistent and aligned with existing package patterns.

To structure Go tests consistently, organize them with subtests, collapse redundant assertions, and keep simple parsers colocated with the types they parse. This ensures test structure aligns with shared repository conventions and produces cleaner diffs.

Yes, you can use this Skill to review or rewrite Go code so it follows shared style conventions before you edit or commit it. This helps catch accidental inconsistency and style drift early in the development process.

You need consistent Go code style conventions for code review when repositories require consistent pointer initialization, import aliasing, logger naming, test structure, assertion usage, and parser placement to stay grepable and aligned with existing package patterns.