Individual skill
go-concurrency-pipelines
Design, implement, test, and review bounded in-process Go concurrency using goroutines, channels, iterators, mutexes, shared collections, WaitGroup, errgroup, backpressure, ordering, cancellation, and deterministic lifecycle checks. Use when building worker pools, streaming pipelines, concurrent batches, background stages, or diagnosing races, goroutine leaks, blocked operations, synchronization ownership, and shutdown failures.
plugins/LVTD-LLC/skills/skills/go-concurrency-pipelines/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,533
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- go,golang,concurrency,goroutines,channels,pipelines Declared skill tag
- operations Derived category
- design Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,396 bytesagents/openai.yamlasset · 225 bytesguidelines.mddoc · 1,195 bytesreferences/concurrency-pipelines/examples.mddoc · 1,908 bytesreferences/concurrency-pipelines/knowledge.mddoc · 3,292 bytesreferences/concurrency-pipelines/rules.mddoc · 2,905 bytesworkflows/design-cancellable-pipeline.mddoc · 974 bytesworkflows/review-goroutine-lifecycle.mddoc · 805 bytesworkflows/test-concurrency-contract.mddoc · 903 bytes
Read excerpt
# Go Concurrency Pipelines
Every goroutine needs an owner, a stop condition, and a completion path. Bound
admission before optimizing throughput.
## Core Workflow
1. Define input, output, ordering, partial-result, and failure contracts.
2. Prefer a synchronous or iterator API unless callers need channel mechanics.
3. Assign ownership of goroutines, channel closure, timers, and cancellation.
4. Bound concurrency, queues, retries, and memory together.
5. Make every blocking send, receive, and wait cancellation-aware.
6. Join all owned goroutines on success, failure, cancellation, and early exit.
7. Test lifecycle behavior with barriers and deadlines rather than sleeps.