Enforce Go style principles for formatting, naming, and documentation.
npx skills add https://github.com/cxuu/golang-skills --skill go-style-core
Please help me install this Agent Skill. Skill: go-style-core Source: https://github.com/cxuu/golang-skills/tree/main/skills/go-style-core Command: npx skills add https://github.com/cxuu/golang-skills --skill go-style-core
Core Go style principles provide a clear baseline for writing readable, maintainable Go code by enforcing consistency with established style guidelines.
Audit your Go files against the core principles and start refactoring for clarity, simplicity, and consistency.
High-intent search queries and answers about installing and using this skill.
You can enforce Go style by applying core principles like gofmt formatting and MixedCaps naming to improve readability and maintainability across packages. This provides a clear baseline for consistent coding.
Core Go style principles emphasize clarity-first coding with descriptive names, helpful comments, minimal abstractions, and consistent formatting guided by Google and Uber style guidance.
Standardize Go packages by auditing files against core style principles and refactoring for clarity, simplicity, and consistency. This reduces review feedback by establishing a shared formatting and naming baseline.
Yes, this guidance satisfies requirements for gofmt formatting and MixedCaps naming, alongside concise line-length guidance and maintainable control-flow practices for Go projects.
The best way to audit Go files is to check them against core style principles, focusing on explicit rationale, minimal abstractions, and consistent formatting to identify areas for refactoring.
You should avoid minimal abstractions when an explicit rationale or complex control-flow logic requires deeper context, though core Go style generally favors simplicity to maintain codebase readability.
LusciiDesign reusable Terraform modules with standard structures and provider configurations.
TheGreatLAutomate code linting and formatting with Prettier and a linter before commits.
alangebRun pyscan, pyanalyze, ruff, and black to generate a unified markdown report.
ashaykubalExecute static analysis and LLM review to detect security, type, linting, and standard issues.
