go-concurrency-reviewer

To detect goroutine leaks, run a concurrency audit that enforces a phased checklist ensuring every goroutine has a shutdown mechanism, proper context handling, and safe channel usage, generating a remediation report.

Deadlocks and race conditions occur due to unsafe shared state protection and improper synchronization. A deep concurrency audit evaluates patterns, channel safety, and synchronization primitives to identify and remediate these defects.

The best way to audit Go concurrency is using a structured phase-based methodology that dispatches sub-agents to verify lifecycle, shared state protection, channel safety, timer usage, and synchronization primitives across the codebase.

Yes, you can check channel and context safety by running an audit mode that dispatches sub-agents to verify safe channel usage, proper context propagation, and timer or context usage across your Go project.

Yes, the concurrency audit covers established Go patterns and best practices by providing cross-references that link identified defects to deeper learning resources for safe, leak-free code.