BUGLYST.
Sign inStart debugging
Review Lab

Practice catching risky changes before they ship.

Read a pull request the way a senior reviewer does: open the diff, find the line that turns into an incident, and decide whether it can merge. No terminal, no sandbox — just review judgment.

difference3 review casesschedule~20 min totalscoreboardScored out of 100saveProgress saved on this device
Pattern-based practice. Not official, and not affiliated with any company, GitHub/Bitbucket, or upstream project. The pull requests are fictional, anonymized engineering scenarios.

Open pull requests

Refactor auth context middleware#RL-001hard

A cleanup of request-context setup quietly changes how the tenant is resolved. Decide whether it is safe to merge.

persondev-checkout-teamfork_rightrefactor/auth-context1 file+3−12schedule~8m
securitymulti-tenantauthorizationmiddleware
Simplify retry delay handling#RL-002medium

A retry helper is trimmed down to remove some math. Decide whether the new delay logic is production-safe.

persondev-platform-teamfork_rightchore/simplify-retry1 file+1−5schedule~6m
reliabilityretriesbackoffperformance
Clean up cache key builder#RL-003medium

A cache-key helper is shortened. Decide whether the simpler key still keeps data separated correctly.

persondev-api-teamfork_rightchore/cache-key-cleanup1 file+2−8schedule~6m
data-correctnesscachingmulti-tenantregression
scoreboard

How a review is scored

Each review is graded objectively out of 100: flag at least one genuinely risky line (40), pick the right risk category (20), choose the right review decision (20), and name a real reason in your comment (20). After you submit, the expected risky lines and a Buglyst reference review are revealed so you can compare your judgment.