スキル golang-design-patterns

📦

golang-design-patterns

Name: golang-design-patterns
Author: samber

v1.2.1 コンテンツリビジョン r1 中リスク ⚙️ 外部コマンド🔑 環境変数⚡ スクリプトを含む🌐 ネットワークアクセス

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.

対応: Codex Code(CC)

📊 70 十分

Maintain this Skill? Claim it 📊 70 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/samber-golang-design-patterns.md 署名済み manifest GET /api/skills/samber-golang-design-patterns/manifest 署名済み lockfile GET /api/skills/samber-golang-design-patterns/lockfile

テストする

「golang-design-patterns」を使用しています。 What architecture should I use for a small CSV-processing CLI?

期待される結果:

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.

「golang-design-patterns」を使用しています。 Our service opens its database in init and has no shutdown deadline. What should change?

期待される結果:

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.

「golang-design-patterns」を使用しています。 How should Order and Billing communicate in a DDD application?

期待される結果:

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.

セキュリティ監査

中リスク

v1 • 2026/10/15 バージョン別レポートを開く

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.

スキャンされたファイル

1,779

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (1)

中

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.

リスク要因

⚙️ 外部コマンド (50)

🔑 環境変数 (2)

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

⚡ スクリプトを含む (2)

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

🌐 ネットワークアクセス (1)

SKILL.md:12

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

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

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)

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>

埋め込みカード

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

学術引用 (APA · BibTeX · CFF)

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

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"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

100

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

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.

これらのプロンプトを試す

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.

ベストプラクティス

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.

回避

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.