Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/golang-patternsAPI, SaaS e identità

golang-patterns

⁨Idiomatic Go patterns, best practices, and conventions for building robust, readable, and maintainable Go code. Use when writing, reviewing, or refactoring Go (APIs, packages, errors, interfaces, concurrency, code style), choosing a dispatch or plugin mechanism, or building low-level/offensive Go wi⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/golang-patterns

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
PzN2bSQgJn…9LxPDeCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto13b96c40…83d344dd
13b96c40d986…a61e83d344dd14 file · ⁦29.4 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/golang-patterns@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

This skill focuses on idiomatic Go design and code review guidance.

If your task is primarily measurement/profiling/optimization, use golang-performance.

When to activate

  • Writing new Go code (packages, APIs, services)
  • Reviewing PRs for idioms, readability, and maintainability
  • Refactoring for cleaner error handling and smaller interfaces
  • Designing concurrency flows with cancellation and backpressure
  • Choosing a dispatch/plugin mechanism, adding modules to a compiled binary, or building low-level/offensive Go tooling

Core principles (high signal)

  • gofmt is non-negotiable. Style debates end at gofmt.
  • Prefer clarity: small functions, early returns, explicit control flow.
  • Make the zero value useful.
  • Keep interfaces small; define them where they’re consumed.
  • Handle errors explicitly; wrap with context; avoid panic for control flow.
  • Concurrency should be bounded and cancellable; avoid goroutine leaks.

Outcome expectations

  • Public APIs are small, explicit, and boring to maintain.
  • Error handling is consistent and machine-checkable with errors.Is / errors.AsType.
  • Concurrency flows always have cancellation and backpressure.
  • Tooling baseline (gofmt, tests, vet/race) is easy to run in CI.

  1. Define package boundary + API contracts (inputs, outputs, errors) first.
  2. Implement with small functions and explicit control flow.
  3. Add context propagation and cancellation checks on blocking operations.
  4. Run formatting/tests/vet/race before review.
  5. Review for leaks, hidden globals, and interface over-abstraction.

Quick review checklist

  • Naming: MixedCaps for exported, no underscores, packages short and lower-case
  • Errors: fmt.Errorf("context: %w", err), errors.Is / errors.AsType (Go 1.26+) used correctly
  • Context: ctx is first param; cancellation propagates; no context.Context stored in structs
  • Interfaces: accept interfaces, return concrete types; no “kitchen-sink” interfaces
  • Concurrency: goroutines have a stop condition; channels are closed by senders; backpressure exists
  • Tooling: go test ./..., go test -race ./..., go vet ./...

Common anti-patterns to reject

  • Storing context.Context in structs
  • Unbounded goroutine fan-out in request paths
  • Catch-all interfaces like Doer, Manager, Service without clear boundary
  • Returning wrapped errors without enough domain context
  • Package-level mutable state hidden behind helper functions

Resources

Load on demand (progressive disclosure):

  • references/effective-go.md — distilled Effective Go + Code Review Comments pointers
  • references/language.md — load when using loop-var/range-over-func semantics, new(expr), self-referential constraints, generic methods, embedded-field keys, or 1.27 type inference
  • references/json-v2.md — load when adding or migrating JSON (encoding/json vs encoding/json/v2, omitzero, stricter defaults)
  • references/errors.md — wrapping, sentinel vs typed errors, errors.AsType, validation, retryable errors
  • references/interfaces.md — interface placement, design patterns, optional behavior, generic-method vs interface-method rule
  • references/concurrency.md — cancellation, errgroup, leaks, worker pools, backpressure, timer-channel semantics
  • references/api-and-structs.md — receiver rules, functional options, embedding, ServeMux patterns
  • references/package-layout.md — project layout, package naming, dependency injection
  • references/tooling.md — gofmt/goimports, vet, go fix, language version via the go directive
  • references/security-review.md — use when auditing Go for security bugs: untrusted input, panics/DoS, TLS defaults, secrets, supply chain (govulncheck, gosec)
  • references/unsafe-cgo.md — use for unsafe.Pointer rules, syscall/x/sys, cgo boundaries, and static/cross-compiled offensive-tooling builds
  • references/dispatch-and-plugins.md — use when choosing dyn interfaces vs enum dispatch, building registries and command dispatchers, or adding modules to a compiled binary (plugin, hashicorp/go-plugin, wazero/extism, yaegi, selfupdate, tableflip)
  • references/offensive-lowlevel.md — use for RE-resistance, symbol/metadata stripping, garble/GoReSym, string obfuscation, syscall dispatch strategy, and in-memory execution

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileSìSì
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd56813b96c40Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login