A PRACTICAL NOTE · Daily workflows

How to apply this guide

Speak the issue, location and requested change while protecting code identifiers and technical meaning.

Start with

Say “In the profile loader, is the retry limited when the server returns a timeout?” Type the exact file or function identifier after capture if the recognizer is likely to alter it.

Check before you finish

Use the comment draft and verify the cursor position. Paste from the reviewed result when a custom code editor does not support direct insertion. Submit the review when you are ready.

Evidence to keep: Keep the target field open and verify that the complete reviewed result reached the intended destination. This page’s key limit is: Speak the issue, location and requested change while protecting code identifiers and technical meaning.

Start here

Dictation saves typing on longer review notes, but punctuation-heavy identifiers often need manual correction. Define the outcome before speaking: a question, suggestion or request.

Explain the issue first

Say “In the profile loader, is the retry limited when the server returns a timeout?” Type the exact file or function identifier after capture if the recognizer is likely to alter it.

Preserve the reviewer’s intent

Check wording such as “could,” “must” and “only.” An optional formatter may make a tentative question sound like a required change. Compare with the original and correct the final text.

Check the target field

Use the comment draft and verify the cursor position. Paste from the reviewed result when a custom code editor does not support direct insertion. Submit the review when you are ready.

Keep exploring