Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/golang-patternsAPIs, SaaS e identidade

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-patterns

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
PzN2bSQgJn…9LxPDeCQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote13b96c40…83d344dd
13b96c40d986…a61e83d344dd14 arquivos · ⁦29.4 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
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.

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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. 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ãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd56813b96c40Assinada–

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. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login