Goroutine Leak Testing

When to use

• Code contains goroutine patterns (go func(), go methodCall())
• After implementation or during code review
• Suspected memory leak in production
• Need to verify goroutine-heavy code doesn't leak

Skip when

• Codebase contains no goroutine usage
• Not a Go project
• Task is documentation-only, configuration-only, or non-code
• Changes do not touch any concurrent code paths

Sequence

Runs before: ring:reviewing-code Runs after: ring:implementing-tasks