Covers the mechanics of writing and organizing Go functions: signature formatting, call ordering, receiver grouping, and when to wrap long parameter lists. Includes guidance on pointers to interfaces (you almost never need them), Printf-style naming conventions for format string functions, and using %q over %s for safer string formatting in logs and errors. The file ordering rules are especially practical: types first, then constructors, exported methods, unexported ones, then utilities. It deliberately excludes functional options constructors and error handling patterns, which have their own dedicated skills. If you're refactoring a Go file and wondering where functions should live or how to format a ten-parameter signature, this is the reference.
npx skills add https://github.com/cxuu/golang-skills --skill go-functions