Prepare the source
Use a demo environment or a code view without secrets. Record the change, the behavior it affects and the checks you ran. State the branch or revision separately in your review so the recording has a stable reference.
Explain the relevant code paths instead of scrolling through unrelated files.
Try this prompt
Open or attach the recording in Ask AI, then adapt this example to your task:
Create review notes from this walkthrough. Describe the behavior change, rationale, checks mentioned and open questions. Do not claim tests passed unless the recording says so. Add source timestamps.
Check the result
Check the notes against the actual diff and test output. A recording can explain a change but cannot establish that the entire codebase is correct or secure.
Copy the reviewed notes into your code-review workflow and link the recording where useful. Confirm that its audience has permission to view the code shown.