Identify and fix Go data-type mistakes in slices, maps, and numeric literals.
npx skills add https://github.com/v0lka/skills --skill go-data-types
Please help me install this Agent Skill. Skill: go-data-types Source: https://github.com/v0lka/skills/tree/main/development/idiomatic-go/go-data-types Command: npx skills add https://github.com/v0lka/skills --skill go-data-types
Go developers frequently trip over data-type pitfalls in slices, maps, and numeric literals, causing subtle bugs, performance issues, or incorrect program behavior.
Audit your Go codebase to identify the top 2-3 data-type pitfalls and apply proven patterns to fix slices, maps, and numeric literals.
High-intent search queries and answers about installing and using this skill.
Prevent Go integer overflow and floating-point precision issues by applying proper initialization patterns, checking literal prefixes for octal confusion, and verifying arithmetic boundaries to ensure correct program behavior.
Incorrect Go map or slice memory usage often stems from misunderstanding capacity, length, and initialization semantics, which can be fixed by applying correct initialization patterns and reasoning about memory allocation during refactoring.
The best way to identify and fix Go numeric literal and overflow bugs is to audit literal prefixes to prevent octal confusion and apply proven patterns to handle integer overflow, NaN, and floating-point precision correctly.
Yes, you can use Go data-type guidelines for both development and code education, as they provide practical examples and proven patterns to prevent common mistakes with slices, maps, and numeric literals across typical scenarios.
vlad-ryzhkovAudit Go backend repositories for API endpoints, infrastructure, and test coverage.
rizaldiemValidate boundary and edge-case behaviors in JUnit 5 tests.
ozan-fnAnalyze Go code for nil safety, concurrency, and resource management issues.
Utchash007Apply defensive Go patterns to prevent panics and data corruption.
