Write concurrent Go code without goroutine leaks.
What it does
Guides concurrent Go implementation and review to prevent goroutine leaks, ownership violations, and unprotected shared state.
When to use it
Use when writing or reviewing concurrent Go code, choosing synchronization primitives, protecting shared maps or counters, or checking goroutines without clear exits.
How to use it
It changes how the agent writes, reviews, and audits concurrent Go code by applying lifecycle, cancellation, ownership, and synchronization checks.
What you provide
- An existing project
Good to know
- starts 5 helper agents
Latest review
What you need · 1
Requires the go binary; the guidelines also call for running project tests with the race detector.
Access · 0
No additional actions listed.