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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/golang-patternsGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote13b96c40…83d344dd
13b96c40d986…a61e83d344dd14 arquivos · 29.4 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/AeonDave/malskill/tree/main/coding/golang-patterns@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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
panicfor 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.
Recommended workflow
- Define package boundary + API contracts (inputs, outputs, errors) first.
- Implement with small functions and explicit control flow.
- Add context propagation and cancellation checks on blocking operations.
- Run formatting/tests/vet/race before review.
- 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:
ctxis first param; cancellation propagates; nocontext.Contextstored 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.Contextin structs - Unbounded goroutine fan-out in request paths
- Catch-all interfaces like
Doer,Manager,Servicewithout 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 pointersreferences/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 inferencereferences/json-v2.md— load when adding or migrating JSON (encoding/jsonvsencoding/json/v2,omitzero, stricter defaults)references/errors.md— wrapping, sentinel vs typed errors,errors.AsType, validation, retryable errorsreferences/interfaces.md— interface placement, design patterns, optional behavior, generic-method vs interface-method rulereferences/concurrency.md— cancellation, errgroup, leaks, worker pools, backpressure, timer-channel semanticsreferences/api-and-structs.md— receiver rules, functional options, embedding, ServeMux patternsreferences/package-layout.md— project layout, package naming, dependency injectionreferences/tooling.md— gofmt/goimports, vet,go fix, language version via thegodirectivereferences/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 forunsafe.Pointerrules,syscall/x/sys, cgo boundaries, and static/cross-compiled offensive-tooling buildsreferences/dispatch-and-plugins.md— use when choosingdyninterfaces 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
Arquivos desta versão
references/1367.0 KB
- api-and-structs.md1.8 KB
- concurrency.md4.3 KB
- dispatch-and-plugins.md11.1 KB
- effective-go.md3.9 KB
- errors.md3.0 KB
- interfaces.md1.9 KB
- json-v2.md3.9 KB
- language.md5.6 KB
- offensive-lowlevel.md11.1 KB
- package-layout.md814 B
- security-review.md8.7 KB
- tooling.md2.3 KB
- unsafe-cgo.md8.6 KB
- SKILL.md5.0 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 13b96c40 | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em APIs, SaaS e identidade
Ver a categoria- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login