Review-Ready Code

Transform a completed implementation into a review representation that is easier for a human to understand. The implementation branch remains the source of truth; the review-ready branch is a disposable projection of the same final tree with a deliberately structured commit history.

Source Method

At every invocation, fetch and read Google's current Small CLs guidance before choosing commit boundaries:

• Google Engineering Practices — Small CLs

Do not rely only on remembered summaries of the article. If the source cannot be fetched, report that limitation before reorganizing the history.

Use the article as the method for deciding what constitutes a reviewable change. In particular, prefer one self-contained conceptual change, keep related tests with the behavior they verify, separate meaningful refactors from behavior changes, and choose horizontal or vertical splits according to which makes each change independently understandable.

Invariant

This workflow changes history and presentation only, never the completed implementation.

Capture the finished implementation by immutable commit ID before doing anything else: