go-dev

Generate and run Go benchmarks with profiling and optimization analysis

Auto-detect build system, parse errors, and fix until clean

Cancel any active persistent loop

Deep-dive explanation of Go code with diagrams

Auto-fix Go linting issues with golangci-lint

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 general Go development question. Trigger this skill liberally for ANY Go-related development work as a routing hub to specialized skills. WHEN NOT: Non-Go languages, questions entirely unrelated to programming

WHEN: User is organizing Go code, asking about package structure, naming conventions, project layout, import organization, file organization, or asking "where should I put this?", "how should I name this package?", "should I split this file?". Also when reviewing code organization in PRs or refactoring package boundaries. WHEN NOT: Non-Go languages. Interface design specifics (use go-interfaces). Concurrency patterns (use go-concurrency).

WHEN: User is writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Also when detecting goroutine leaks, race conditions, channel ownership issues, or choosing between channels and mutexes. WHEN NOT: Non-Go languages. Sequential code with no concurrency needs. Performance profiling (use go-profiling-optimization). Debugging race conditions (use systematic-debugging).

WHEN: User is creating, wrapping, inspecting, or logging errors in Go code. Also when reviewing error handling in PRs, asking about error patterns, using fmt.Errorf, errors.Is, errors.As, errors.Join, sentinel errors, custom error types, or panic/recover. WHEN NOT: Non-Go languages. Performance profiling (use go-profiling-optimization). General debugging (use systematic-debugging).

WHEN: User is designing interfaces, asking about interface patterns, implementing interfaces, working with type assertions, type switches, embedding, or asking "should this be an interface?", "where should I define this interface?", "how many methods should my interface have?". Also activate when reviewing interface design in PRs or refactoring toward interfaces. Trigger when user mentions io.Reader, io.Writer, fmt.Stringer, sort.Interface, interface composition, interface embedding, type assertion, type switch, implicit satisfaction, decorator pattern, middleware pattern, or any question about Go interface design. Trigger this skill liberally for ANY Go interface-related work. WHEN NOT: Non-Go languages. Concurrency primitives (use go-concurrency). Error handling specifics (use go-error-handling).