WEBVTT

NOTE Timing: local ASR word timestamp alignment. Review against audio before publishing.

00:00:00.000 --> 00:00:02.760
Let's turn a code review into precise feedback.

00:00:03.820 --> 00:00:06.740
We'll select code, leave two comments, and send

00:00:06.740 --> 00:00:09.400
them together, so pi gets the questions and

00:00:09.400 --> 00:00:09.900
their context.

00:00:10.750 --> 00:00:12.950
These edits were prepared for our fictional demo.

00:00:13.690 --> 00:00:15.630
Open the changed files and compare the search

00:00:15.630 --> 00:00:16.870
logic side by side.

00:00:17.500 --> 00:00:20.760
Select the task-ID line, then extend the selection

00:00:20.760 --> 00:00:23.720
across the search fields. Add a question about

00:00:23.720 --> 00:00:25.760
that code and save it to the batch.

00:00:26.500 --> 00:00:28.740
Now open the test and select the relevant

00:00:28.740 --> 00:00:32.280
lines. Add a second question about lowercase searches.

00:00:33.280 --> 00:00:35.660
Each comment keeps its own file and selected

00:00:35.660 --> 00:00:36.100
code.

00:00:36.750 --> 00:00:39.610
Both comments are queued, not sent yet. Use

00:00:39.610 --> 00:00:41.790
the file chips to revisit a comment before

00:00:41.790 --> 00:00:42.850
handing over the batch.

00:00:43.500 --> 00:00:46.200
When you're ready, send both comments to pi

00:00:46.200 --> 00:00:50.360
together. They become one message, rather than two

00:00:50.360 --> 00:00:51.460
separate interruptions.

00:00:52.083 --> 00:00:54.523
The conversation keeps both comments with their file

00:00:54.523 --> 00:00:57.683
references and quoted code. pi can address the

00:00:57.683 --> 00:01:00.843
feedback from the same context, without retyping the

00:01:00.843 --> 00:01:01.123
selections.