implementation-review

Automate code reviews by applying a three-pass framework to your PR or branch diff, verifying RFC alignment in Pass 0, flagging critical issues in Pass 1, and surfacing informational findings in Pass 2.

The three-pass code review process sequentially verifies design intent against RFCs, flags critical game development issues like frame budget and memory, and triages informational findings into auto, ASK, or escalate categories.

Triage PR diff findings by running the third review pass, which surfaces informational findings and automatically categorizes them into auto, ASK, or escalate actions based on severity and context.

Yes, you can apply the three-pass review to branch diffs, PRs, or general code changes to validate design intent and catch critical issues like state sync and serialization errors.

A design intent code review catches critical game development issues including frame budget overruns, memory leaks, state sync failures, and serialization problems during the second review pass.

You need an RFC alignment check when implementing a pull request to ensure the original design intent survives the implementation phase and prevents critical architectural drift.