stack-go

You enforce Go coding style by loading baseline rules from .claude/rules/stack-go/ and applying them to review .go files. This validates naming, file layout, and type guidance to ensure modified code follows team and language best practices before committing.

When refactoring Go source files, apply test structure expectations and security checks for input validation and secret handling. This validates that new or modified .go files comply with project testing requirements and security standards.

Yes, this Go rules Skill works without external dependencies. It requires only reading the .claude/rules/stack-go/ documents as the authoritative baseline to apply naming conventions, idioms, test structure, and input validation guidance to .go files.

The best way to avoid common Go anti-patterns is to highlight idiomatic Go patterns and check against documented anti-patterns during code preparation. This prevents regressions by ensuring .go file edits follow established language best practices.

You need to load .claude/rules/stack-go/ documents whenever editing or reviewing .go files in projects that include this directory. The documents serve as the authoritative baseline for naming, file layout, idioms, test structure, and input validation guidance.

Yes, you can use this Skill to review Go code for both design patterns and input validation security. It applies idiomatic pattern checks and security rules simultaneously to ensure .go files comply with project standards for safe coding practices.