Reviews Go code for idiomatic patterns, error handling, concurrency safety, and common mistakes. Use when reviewing .go files, checking error handling, goroutine usage, or interface design.
Expert senior-level Go guidance for architecture, API-first design/codegen, advanced concurrency, performance tuning, testing/quality, cloud-native 12-factor practices, and Go 1.24+ tooling for...
Reviews Go test code for proper table-driven tests, assertions, and coverage patterns. Use when reviewing *_test.go files.
Go ๅผๅ่ง่๏ผๅ ๅซๅฝๅ็บฆๅฎใ้่ฏฏๅค็ใๅนถๅ็ผ็จใๆต่ฏ่ง่็ญ
Expertise in Go programming decisions according to the Google Go Style Guide. Focuses on specific choices for naming, error handling, and language usage.
Use this skill to write, refactor, or review Go code according to the Uber Go Style Guide. It ensures strict adherence to correctness, safety, and idiomatic patterns.
Generate high-quality Go unit tests for the given code or function.
Shared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
Expert in generating functional options for Go structs using the options-gen library.
Maintain Go repositories with high-quality standards, adhering to CI/CD, linting, and agent-friendly best practices.
Go API development guidelines using the standard library (1.22+) with best practices for RESTful API design, error handling, and security
Generate table-driven Go tests (unit or integration) for given functions, handlers, or packages. Use when the user asks for tests, coverage, regression prevention, or test scaffolding with mocks/fakes.
Audit Go code for concurrency bugs: data races, goroutine leaks, deadlocks, channel misuse, and context leaks. Use when the user mentions goroutines, worker pools, timeouts, stuck requests, high...
Go backend development best practices for microservices with clean architecture, observability, and production-ready patterns
Plan product launches and go-to-market strategy. Use when launching products, entering new markets, or planning marketing campaigns. Covers positioning, channels, messaging, and launch execution.
Reviews Prometheus instrumentation in Go code for proper metric types, labels, and patterns. Use when reviewing code with prometheus/client_golang metrics.
|
|
>
Best practices for writing production Go code. Use when writing, reviewing, or refactoring Go code. Covers error handling, concurrency, naming conventions, testing patterns, performance...