Skip to main content
An understanding check is a set of questions for one change request and source revision. Questions focus on behavior, intent, data flow, tradeoffs, and system impact. They use the change and its available context rather than unrelated trivia.

​
Complete a check

Open the understanding-check link from the pull request and sign in with the same account you use for the Second Flow console. Read each question and the sources provided with it. Depending on the question, you may choose an option, enter an exact answer, or write a free-form explanation. Your responses together form the explanation you submit with Complete check. Explain the behavior in your own words. For example, describe what changes, why it changes, and what happens at an important boundary or failure condition.

​
Review the result

A result records the outcome of a submitted explanation. Completed results are read-only. Feedback helps you understand the change and identify gaps in your explanation. If the repository uses passing standards, the result is evaluated against its configured threshold. That outcome applies to the repository policy; it does not label the engineer.

​
Changes and retakes

A check belongs to a specific source revision. New commits can supersede an unsubmitted check. Use the current link on the pull request when the code changes. After a completed result, a retake creates a new understanding check with varied questions. A passing result satisfies the policy for the corresponding change-request head revision.

​
When no check is needed

Not every pull request supports useful questions. Documentation-only and trivial changes can receive an explanatory comment and a neutral repository outcome. Second Flow does not add questions just to reach a target count.