Loading...
Loading...
Found 19 Skills
A comprehensive guide for using Testcontainers for Go to write reliable integration tests with Docker containers in Go projects. Supports 62+ pre-configured modules for databases, message queues, cloud services, and more.
Develop Go (Golang) applications using modern patterns, popular libraries, and idiomatic design. Activate when working with .go files, go.mod, go.sum, or user mentions Go, Golang, goroutines, channels, or Go libraries like gin, cobra, gorm.
Quick-reference checklist for Go code review based on the Go Wiki CodeReviewComments. Maps to detailed skills for comprehensive guidance. Use when reviewing Go code or checking code against community style standards.
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
WHEN: User is writing Go code, asking about Go patterns, reviewing Go code, asking "what's the best way to...", "how should I structure...", "is this idiomatic?", or any question about error handling, concurrency, interfaces, packages, testing patterns, or code organization in Go. Also activate when user is debugging Go code, refactoring Go, or working in a Go project (go.mod present) and asks general coding questions. Trigger this skill liberally for ANY Go-related development work. WHEN NOT: Non-Go languages, questions entirely unrelated to programming
Deep dive on table-driven tests in Go: when to use them, when to avoid them, struct design, subtest naming, advanced patterns like test matrices and shared setup, and refactoring bloated tables into clean ones. Use when writing table-driven tests, refactoring test tables, reviewing table test structure, or deciding whether table-driven is the right approach. Trigger examples: "table-driven test", "table test", "test cases struct", "test matrix", "parametrize tests", "data-driven test", "refactor test table". Do NOT use for general test strategy, mocking, golden files, or fuzz testing (use go-test-quality). Do NOT use for benchmarks (use go-performance-review).
Guide for writing idiomatic, effective, and standard Go code. Use this skill when writing, refactoring, or reviewing Go code to ensure adherence to established conventions and best practices.