cc-go-concurrency
Use when Go goroutine leaks, channel ownership, cancellation propagation, synchronization, worker bounds or race conditions need implementation or diagnosis.
SKILL.mdskills/cc-go-concurrency/SKILL.md
GitHubGo concurrency lifecycle
Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.
List goroutine starters, stop signals, blocking operations and the party that waits for completion. A request return does not prove worker exit.
Apply the workflow
- Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now.
- Apply the specialist checks, establishing the input evidence before selecting the smallest change.
- Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result.
- Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.
Task boundary
Use broader Go engineering guidance for module/package organization; buffering alone does not establish a safe lifecycle.
Engineering practices
Read the local engineering decisions for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.