Habilidades golang-design-patterns

📦

golang-design-patterns

Name: golang-design-patterns
Author: samber

v1.2.1 Revisión del contenido r1 Riesgo medio ⚙️ Comandos externos🔑 Variables de entorno⚡ Contiene scripts🌐 Acceso a red

Design Idiomatic Go APIs and Architecture

Go services become harder to maintain when initialization, resource ownership, and architectural boundaries are unclear. This skill guides practical pattern selection with focused Go examples.

Compatible con: Codex Code(CC)

📊 70 Adecuado

Maintain this Skill? Claim it 📊 70 Adecuado

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente

Review the Skillstore skill "golang-design-patterns" from https://skillstore.io/skills/samber-golang-design-patterns.md and its manifest at https://skillstore.io/api/skills/samber-golang-design-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/samber-golang-design-patterns.md Manifest firmado GET /api/skills/samber-golang-design-patterns/manifest Lockfile firmado GET /api/skills/samber-golang-design-patterns/lockfile

Pruébalo

Usando "golang-design-patterns". What architecture should I use for a small CSV-processing CLI?

Resultado esperado:

Confirm team preferences and expected growth before adding layers.
Use a flat layout with a small entry point and focused transformation functions.
Introduce additional packages only when responsibilities or testing needs justify them.

Usando "golang-design-patterns". Our service opens its database in init and has no shutdown deadline. What should change?

Resultado esperado:

Finding: Implicit database initialization hides dependencies and prevents normal error propagation.
Recommendation: Open the database explicitly during startup and inject it into repositories.
Finding: Shutdown can wait indefinitely without a separate deadline.
Recommendation: Handle termination signals, drain requests with a timeout, then close shared resources.

Usando "golang-design-patterns". How should Order and Billing communicate in a DDD application?

Resultado esperado:

Keep each bounded context responsible for its own domain model.
Publish an order event and translate it into a billing-specific representation.
Avoid importing another context's internal domain types directly.

Auditoría de seguridad

Riesgo medio

v1 • 15/10/2026 Abrir el informe versionado

All 89 static findings are false positives involving documentation syntax, ordinary Go constructs, illustrative configuration access, and homepage metadata. One semantic finding identifies internal errors returned directly to HTTP clients in two architecture examples. No evidence found of credential exfiltration, malicious command execution, or instructions to manipulate this audit.

Archivos escaneados

1,779

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (1)

Medio

references/clean-architecture.md:174-176 references/hexagonal-architecture.md:169-171

Internal Errors Exposed in HTTP Responses

Both architecture handlers pass err.Error() directly to http.Error. Wrapped repository or payment failures can expose infrastructure diagnostics to clients when these examples are adopted.

Both handlers explicitly write service error strings to response bodies without message sanitization. The exact disclosed details depend on downstream errors.

Factores de riesgo

⚙️ Comandos externos (50)

🔑 Variables de entorno (2)

evals/evals.json:35 SKILL.md:124

⚡ Contiene scripts (2)

references/ddd.md:158-163 references/ddd.md:199-202

🌐 Acceso a red (1)

SKILL.md:12

Auditado por: codex

Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado

Copiar enlace del informe

https://skillstore.io/skills/samber-golang-design-patterns/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Insignia Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-design-patterns/security.svg)](https://skillstore.io/skills/samber-golang-design-patterns?utm_source=security_passport_badge)

Insignia HTML

<a href="https://skillstore.io/skills/samber-golang-design-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-design-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/samber-golang-design-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citas académicas (APA · BibTeX · CFF)

Cita APA

samber. (2026). golang-design-patterns security audit report (audit version 1) [Author version 1.2.1]. Skillstore. https://skillstore.io/skills/samber-golang-design-patterns/audits/1

Cita BibTeX

@techreport{samber-samber-golang-design-patterns-2026,
  author = {samber},
  title = {golang-design-patterns security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-design-patterns/audits/1},
  note = {Author version 1.2.1}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-design-patterns security audit report (audit version 1)"
version: "1.2.1"
type: report
authors:
  - name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-design-patterns/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-design-patterns:audit:1"
    description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio

Arquitectura

100

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

Design an Extensible Constructor

Define defaults, optional settings, and validation behavior for a Go library API that will evolve.

Review Service Resource Lifecycles

Identify hidden initialization, missing timeouts, unbounded pools, and incomplete shutdown handling before changing a service.

Choose Application Boundaries

Compare architecture styles for a growing service with multiple entry points and external integrations.

Prueba estos prompts

Beginner: Choose a Simple Layout

I am building a Go CLI that transforms a CSV file. It should remain small. Ask about my architecture preference, then recommend a minimal layout.

Intermediate: Design Functional Options

Design a Go server constructor with read timeout, write timeout, and maximum connections. Use explicit defaults and explain how invalid options return errors.

Experienced: Review Lifecycle Risks

Review the attached Go service for implicit initialization, resource leaks, missing timeouts, and cancellation handling. Report findings first, then suggest focused changes and shutdown ordering.

Advanced: Compare Architecture Styles

Our Go order service has HTTP, gRPC, and message consumers with database and payment integrations. Ask about team preferences. Compare clean, hexagonal, and DDD approaches, including dependency direction and testability.

Mejores prácticas

State the Go version, project scope, and team architecture preferences before requesting design guidance.
Keep resource ownership explicit and review cancellation, limits, and shutdown ordering together.
Adapt illustrative examples to local conventions and verify behavior with focused tests and security review.

Evitar

Adding clean architecture or DDD layers to a small CLI without a concrete need.
Hiding runtime dependencies in init functions or mutable global variables.
Copying illustrative handlers into production without validating error disclosure and project-specific security requirements.