Fähigkeiten golang-concurrency

📦

golang-concurrency

Name: golang-concurrency
Author: samber

v1.2.1 Inhaltsrevision r1 Mittleres Risiko ⚙️ Externe Befehle🌐 Netzwerkzugriff

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.

Unterstützt: Codex Code(CC)

📊 70 Angemessen

Maintain this Skill? Claim it 📊 70 Angemessen

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/samber-golang-concurrency.md Signiertes manifest GET /api/skills/samber-golang-concurrency/manifest Signiertes lockfile GET /api/skills/samber-golang-concurrency/lockfile

Testen

„golang-concurrency“ wird verwendet. Review a function that calls WaitGroup.Add inside each new goroutine.

Erwartetes Ergebnis:

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“ wird verwendet. Choose synchronization for a cache with frequent writes to overlapping keys.

Erwartetes Ergebnis:

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“ wird verwendet. Audit a fan-in function whose input channels may stay open after cancellation.

Erwartetes Ergebnis:

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.

Sicherheitsaudit

Mittleres Risiko

v1 • 15.10.2026 Versionsbericht öffnen

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.

Gescannte Dateien

1,304

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Bestätigte Sicherheitsbedenken (1)

Mittel

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.

Risikofaktoren

⚙️ Externe Befehle (50)

🌐 Netzwerkzugriff (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

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

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

Markdown-Badge

[![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-Badge

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

Einbettungskarte

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

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

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

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

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

100

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

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.

Bewährte Praktiken

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.

Vermeiden

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.