fabianoflore
11 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
fabianoflorentinogolang-design-patterns
Idiomatic Golang design patterns — functional options, constructor APIs, init() and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go p
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-google-wire
Compile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wiregen.go. Apply when using or adopting google/wire, when the codebase imports github.com/google/wire, or when wiring an application graph at compile time via wire.Build. For runtime DI with reflection, see fabianoflorentino/golang-agent-skills@g
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-lint
Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive. Not for wiring a lint step into a GitHub Actions pipeline (→ See
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-modernize
Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for structural refactors, extracting functions, or moving code between packages (→ See fabianoflorentino/golang-agent-skills@golang-refactoring skill).
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-pitfalls-concurrency-foundations
Golang concurrency foundations — concurrency vs parallelism, thinking concurrency is always faster, channels vs mutexes, not understanding race problems (data race vs race condition), not understanding workload types (CPU vs I/O bound, GOMAXPROCS), and misunderstanding Go contexts. Distilled from mistakes 55-60 of 100 Go Mistakes and How to Avoid Them. Apply when reasoning about basic Golang concurrency, goroutines, and context usage.
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-pitfalls-data-types
Golang numeric types and data structures — octal literal confusion, integer overflow, floating-point approximations, slice length vs capacity, inefficient slice initialization, nil vs empty slices, emptiness checks, slice copies, append side effects, slice memory leaks, map initialization, map memory leaks, and incorrect value comparison. Distilled from mistakes 17-29 of 100 Go Mistakes and How to Avoid Them. Apply when writing or reviewing Golang code dealing with numbers, slices, maps, or comp
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-pitfalls-strings
Golang strings and bytes — the rune concept, len(s) returning bytes not runes, inaccurate string iteration over rune start indices, misusing trim functions, under-optimized string concatenation with strings.Builder, useless string to byte conversions, and substring memory leaks. Distilled from mistakes 36-41 of 100 Go Mistakes and How to Avoid Them. Apply when writing or reviewing Golang code that manipulates strings, runes, or bytes.
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-samber-ro
Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pi
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-security
Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus gosec SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil p
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.
fabianoflorentinogolang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see fabianoflorentino/golang-agent-skills@golang-stretchr-testify; for measurement methodology see fabianoflorentino/golang-a
- Installationen
- 1
- GitHub Stars
- 0
- Aktualisiert
- 14. Sept.