スキル golang-concurrency

📦

golang-concurrency

Name: golang-concurrency
Author: samber

v1.2.1 コンテンツリビジョン r1 中リスク ⚙️ 外部コマンド🌐 ネットワークアクセス

Design and Review Go Concurrency

Concurrent Go code can hide goroutine leaks, shared-state races, and blocked pipelines. This skill guides implementation and review with lifecycle checklists and synchronization examples.

対応: Codex Code(CC)

📊 70 十分

Maintain this Skill? Claim it 📊 70 十分

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

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

エージェントリクエスト

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

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

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

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

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

テストする

「golang-concurrency」を使用しています。 Review a function that calls WaitGroup.Add inside each new goroutine.

期待される結果:

Wait can return before goroutines register, leaving work running after the function returns.
Register work before launching goroutines and defer completion inside each worker.
For suitable Go 1.25+ tasks, consider WaitGroup.Go; use errgroup when error propagation or cancellation is required.

「golang-concurrency」を使用しています。 Choose synchronization for a cache with frequent writes to overlapping keys.

期待される結果:

Start with a plain map protected by a mutex or RWMutex.
sync.Map targets write-once/read-many or disjoint-key access patterns, so it is not the default choice here.
Keep critical sections short and benchmark the actual workload.

「golang-concurrency」を使用しています。 Audit a fan-in function whose input channels may stay open after cancellation.

期待される結果:

An unconditional channel receive cannot observe cancellation while the input is idle.
Select between cancellation and each receive, and handle closed channels explicitly.
Test cancellation with every input open and idle, then verify all workers and the output closer finish.

セキュリティ監査

中リスク

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

All 66 static alerts are false positives involving formatting, illustrative Go identifiers, documentation links, or localhost profiling commands. No evidence found of malicious instructions, credential theft, or external data exfiltration. One semantic availability finding covers pipeline examples whose blocking receives can prevent cancellation and retain goroutines.

スキャンされたファイル

1,304

解析済み行数

レビュー項目

誤検知を無視

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

中

references/pipelines.md:41-51 references/pipelines.md:123-134

Pipeline receives can ignore cancellation

The square and fanIn examples range over input channels before checking cancellation. Open, idle inputs can retain workers after cancellation; repeated use can exhaust resources.

Both examples check ctx.Done() only after receiving a value. Cancellation cannot unblock their input receives when channels remain open and idle.

リスク要因

⚙️ 外部コマンド (50)

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

evals/evals.json:61 references/sync-primitives.md:308 SKILL.md:12 SKILL.md:140 SKILL.md:141 SKILL.md:153 SKILL.md:154

監査者: codex

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

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

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

レポートリンクをコピー

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

Markdownバッジ

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

HTMLバッジ

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

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/samber-golang-concurrency.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-concurrency security audit report (audit version 1) [Author version 1.2.1]. Skillstore. https://skillstore.io/skills/samber-golang-concurrency/audits/1

BibTeX形式の引用

@techreport{samber-samber-golang-concurrency-2026,
  author = {samber},
  title = {golang-concurrency security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-concurrency/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-concurrency 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-concurrency/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-concurrency:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

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

アーキテクチャ

100

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Build a bounded background worker

Design worker ownership, concurrency limits, error propagation, and shutdown behavior before adding background tasks.

Review concurrent pull requests

Inspect changed goroutines, channel closure, shared state, and cancellation paths using a focused review checklist.

Audit service concurrency

Coordinate a codebase review across lifecycle management, synchronization, channel ownership, and resource bounds.

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

Choose a synchronization primitive

For this Go shared-state example, compare channels, mutexes, and atomics. Recommend the simplest option and explain ownership: [code].

Review a concurrent change

Review this Go diff for goroutine leaks, unsafe channel closure, shared-state races, and missing cancellation. Explain each issue and propose focused fixes: [diff].

Implement bounded concurrent work

Implement [task] in Go [version] with errgroup, a limit of [N], first-error cancellation, and ordered results. Include shutdown tests.

Audit pipeline shutdown

Audit [scope] for channel ownership, blocked receives, cancellation, and concurrency bounds. Coordinate focused reviewers when available; prioritize findings and propose idle-input cancellation tests.

ベストプラクティス

Define each goroutine owner, stop signal, and waiting mechanism before implementation.
Test cancellation during blocked sends and receives, then run race and goroutine leak checks.
Match APIs to the project Go version and justify concurrency limits with workload measurements.

回避

Launching unbounded goroutines without shutdown or waiting mechanisms.
Closing producer channels from consumers or mutating shared data without synchronization.
Copying pipeline examples without testing cancellation when input channels remain open.