golang-style

Enforce Go coding conventions by applying style checks that verify happy-path logic, error wrapping with %w, sentinel errors, godoc comments, line length caps at 120 characters, and proper naming conventions before writing or editing .go files.

Wrap errors with context using %w to preserve the error chain, define package-level sentinel errors for specific conditions, and avoid nested error-handling logic by structuring code around the happy path.

Write godoc-style comments starting with the function or package name, end all comments with periods, and use `go doc` for documentation lookup to ensure your API is properly documented and discoverable.

Yes, apply the style checks to existing .go files to enforce consistent Go conventions, catch quality issues like shadowed identifiers and improper error handling, and standardize documentation across your codebase.

This enforces Go naming conventions, avoids shadowing predeclared identifiers, enforces a 120-character line-length limit, requires period-ending comments, and ensures happy-path code structure throughout your project.