julik-frontend-races-reviewer

To spot frontend race conditions in code reviews, analyze diffs for async UI lifecycles, Stimulus/Turbo patterns, and DOM-timing-sensitive behavior. This process flags lifecycle cleanup gaps, timing mistakes, and concurrent interaction risks for remediation.

Lifecycle cleanup gaps in asynchronous UI components include stale timers, orphaned event listeners, and async tasks that outlive their components. Identifying these timing mistakes prevents degraded UI performance and unexpected state mutations during concurrent interactions.

Yes, race condition detection works with Stimulus and Turbo patterns by recognizing timing mistakes within their specific lifecycles. It analyzes DOM-timing-sensitive flows and concurrent interaction risks to ensure robust frontend performance during dynamic page updates.

To find orphaned event listeners and stale timers in a diff, review timing-sensitive UI changes for async tasks that outlive components. The analysis records findings of lifecycle cleanup gaps and concurrent interaction risks to guide remediation.

The best way to review async frontend lifecycles for concurrent interaction risks is to apply pattern recognition to timing-sensitive diffs. This surfaces stale timers and orphaned listeners, providing clear checkpoints to mitigate race conditions in pull requests.

You should check for DOM-timing-sensitive behavior in frontend code changes whenever pull requests involve asynchronous UI lifecycles or concurrent interactions. Early detection of timing mistakes and cleanup gaps prevents performance degradation and state inconsistencies.