1
00:00:00,000 --> 00:00:01,355
Welcome to the show everyone!

2
00:00:01,435 --> 00:00:05,595
I'm Lachlan Reed, here with James Turner,
and mates, I have to tell you-I am

3
00:00:05,660 --> 00:00:07,748
absolutely stoked about this.

4
00:00:07,818 --> 00:00:12,793
Imagine you're wrapping up a massive
coding session, you're absolutely knackered,

5
00:00:12,813 --> 00:00:15,756
and instead of just getting a list of
complaints from your linter,

6
00:00:15,788 --> 00:00:18,955
your terminal actually rolls up its
sleeves and fixes the mess for you.

7
00:00:19,081 --> 00:00:25,919
Claude Code just dropped versions 2.1.152
and 154, and they've introduced this

8
00:00:25,977 --> 00:00:30,561
incredible new flag: `/code-review --fix`.

9
00:00:30,854 --> 00:00:36,161
It's not just passive nagging anymore;
it's active, direct-to-file edits.

10
00:00:37,000 --> 00:00:40,847
Wait, direct-to-file edits on a code
review command?

11
00:00:40,927 --> 00:00:43,004
That is a massive paradigm shift.

12
00:00:43,114 --> 00:00:47,719
Usually, a code review tool just leaves a
bunch of comments on your pull request and

13
00:00:47,767 --> 00:00:49,317
lets you do the actual legwork.

14
00:00:49,457 --> 00:00:52,117
Now it's actually writing directly to the
workspace?

15
00:00:53,000 --> 00:00:53,877
Spot on, James.

16
00:00:53,984 --> 00:00:56,686
It literally rewrites the files in place.

17
00:00:56,899 --> 00:01:01,320
If it finds a redundant nested loop or a
dodgy variable assignment,

18
00:01:01,347 --> 00:01:05,724
it doesn't just tell you "hey, this is
trash"-it actually refactors it right there

19
00:01:05,777 --> 00:01:06,921
in your local tree.

20
00:01:07,041 --> 00:01:11,238
And they've doubled down on this with a
revamped `/simplify` command,

21
00:01:11,291 --> 00:01:16,280
which is basically a highly targeted,
cleanup-only pass of that `/code-review

22
00:01:16,387 --> 00:01:17,082
--fix`.

23
00:01:18,000 --> 00:01:22,392
Ah, so `/simplify` isn't trying to do
heavy lifting like hunting down edge-case

24
00:01:22,452 --> 00:01:25,633
logical bugs or security vulnerabilities.

25
00:01:25,981 --> 00:01:28,719
It's literally just a aesthetic and
structural pass.

26
00:01:28,826 --> 00:01:33,040
It's looking for things like dead code,
overly verbose conditional blocks,

27
00:01:33,093 --> 00:01:36,401
or redundant helper functions and just
shaving them down.

28
00:01:37,000 --> 00:01:37,640
Exactly!

29
00:01:37,773 --> 00:01:42,038
It's like having a obsessive-compulsive
senior dev hovering over your shoulder,

30
00:01:42,178 --> 00:01:46,909
but instead of annoying you, they just
silently clean up your indentation and merge

31
00:01:46,941 --> 00:01:48,513
your nested `if` statements.

32
00:01:48,813 --> 00:01:51,313
But look, there's a catch here.

33
00:01:51,446 --> 00:01:55,395
Since it's writing straight to your disk,
you've got to treat these commands like

34
00:01:55,451 --> 00:01:57,075
automated workspace commits.

35
00:01:57,342 --> 00:02:02,600
If you run `/simplify` on a dirty git
tree, you are asking for a world of hurt.

36
00:02:03,000 --> 00:02:04,235
Oh, absolutely.

37
00:02:04,582 --> 00:02:07,632
If you don't have a clean working
directory before you execute this,

38
00:02:07,672 --> 00:02:12,588
you have zero way to isolate what *you*
wrote from what the AI just refactored.

39
00:02:12,768 --> 00:02:16,743
The absolute best practice here has to be:
stage your changes,

40
00:02:16,770 --> 00:02:21,463
or commit them, run the command, and then
immediately run a `git diff` to inspect

41
00:02:21,530 --> 00:02:23,143
every single line it changed.

42
00:02:23,283 --> 00:02:27,627
You cannot just blind-trust an agent to
rewrite your local files without a safety

43
00:02:27,687 --> 00:02:27,947
net.

44
00:02:28,000 --> 00:02:28,960
Too right, mate.

45
00:02:29,160 --> 00:02:33,047
I nearly tanked a client's site years ago
by rushing a midnight update,

46
00:02:33,087 --> 00:02:36,732
and let me tell you, checking your diffs
is a habit written in blood.

47
00:02:37,752 --> 00:02:42,966
Now, speaking of workflow efficiency, they
also added a new `skipLfs` option.

48
00:02:43,179 --> 00:02:47,047
If you're working in massive repositories
with heaps of binary assets,

49
00:02:47,087 --> 00:02:51,286
you can skip Large File Storage checks
entirely, which makes the whole plugin

50
00:02:51,337 --> 00:02:54,812
management and initialization phase run
incredibly fast.

51
00:02:55,000 --> 00:03:00,128
That's actually huge because Git LFS can
absolutely crawl when an external tool

52
00:03:00,185 --> 00:03:01,403
starts scanning the tree.

53
00:03:01,951 --> 00:03:06,595
So, by skipping LFS tracking during the
analysis phase, Claude Code gets straight to

54
00:03:06,615 --> 00:03:09,071
the source files it actually knows how to
edit.

55
00:03:09,258 --> 00:03:11,232
It keeps the feedback loop tight.

56
00:03:12,000 --> 00:03:13,759
It's all about speed and safety, really.

57
00:03:13,903 --> 00:03:20,403
With these direct-to-file edits, we're
moving from AI as an advisor to AI as an

58
00:03:20,472 --> 00:03:21,847
active pair programmer.

59
00:03:21,991 --> 00:03:26,649
Just make sure you keep your git history
clean, run `/simplify` to sweep up the

60
00:03:26,729 --> 00:03:30,406
cobwebs, and always, always inspect your
diffs.

61
00:03:30,550 --> 00:03:32,328
That's our show for today.

62
00:03:32,374 --> 00:03:35,054
Thanks for hanging out with us, and we'll
catch you in the next one.

63
00:03:36,000 --> 00:03:36,401
See ya!