[gostyle.getters] Function and method names should not use a "Get" or "get" prefix, unless the underlying concept uses the word "get" (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use "Counts" over "GetCounts". (ref: https://google.github.io/styleguide/go/decisions#getters ): getShebang

[gostyle.getters] Function and method names should not use a "Get" or "get" prefix, unless the underlying concept uses the word "get" (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use "Counts" over "GetCounts". (ref: https://google.github.io/styleguide/go/decisions#getters ): getFileTypeByShebang

[gostyle.getters] Function and method names should not use a "Get" or "get" prefix, unless the underlying concept uses the word "get" (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use "Counts" over "GetCounts". (ref: https://google.github.io/styleguide/go/decisions#getters ): getFileType

[gostyle.nilslices] When designing interfaces, avoid making a distinction between a nil slice and a non-nil, zero-length slice, as this can lead to subtle programming errors. This is typically accomplished by using len to check for emptiness, rather than == nil. (ref: https://google.github.io/styleguide/go/decisions#nil-slices ): ret != nil

[gostyle.nilslices] When designing interfaces, avoid making a distinction between a nil slice and a non-nil, zero-length slice, as this can lead to subtle programming errors. This is typically accomplished by using len to check for emptiness, rather than == nil. (ref: https://google.github.io/styleguide/go/decisions#nil-slices ): ret != nil

[gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): GCS

[gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS

[gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS

[gostyle.mixedcaps] Go source code uses MixedCaps or mixedCaps (camel case) rather than underscores (snake case) when writing multi-word names. (ref: https://google.github.io/styleguide/go/guide#mixed-caps ): FS

[gostyle.dontpanic] Don't use panic for normal error handling. Use error and multiple return values. (ref: https://go.dev/wiki/CodeReviewComments#dont-panic )