go-data-types

Identify and fix Go data-type mistakes in slices, maps, and numeric literals.

15|Updated Mar 4, 2026

Search Tags:#go #type-safety #code-review #maps #overflow #slices #floating-point

Ready to run

npx skills add https://github.com/v0lka/skills --skill go-data-types

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go developers frequently trip over data-type pitfalls in slices, maps, and numeric literals, causing subtle bugs, performance issues, or incorrect program behavior.

Core Features & Use Cases

Avoid octal confusion by clarifying literal prefixes and proper parsing.
Understand and prevent integer overflow, NaN, and floating-point precision issues.
Correctly initialize slices and maps, reason about capacity, length, and memory usage in real-world code.
Use cases: code reviews, refactoring, and education to prevent common Go mistakes.

Quick Start

Audit your Go codebase to identify the top 2-3 data-type pitfalls and apply proven patterns to fix slices, maps, and numeric literals.

Frequently Asked Questions about go-data-types

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I avoid common Go data-type mistakes with slices and maps during code review?▼

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.

Why does my Go map or slice have incorrect memory usage after refactoring?▼

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.

What is the best way to identify and fix Go numeric literal and overflow bugs?▼

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.

Can I use Go data-type guidelines for both development and code education?▼

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.