Code Tours are pretty awesome and definitely better than $competitor1 and $competitor2's versions I've tried since it intersperses it with prose instead of just headings. I was confused that the code came before the heading/explanation. It seems like the header and prose should come first, and then the code. And of course, setting a file as Viewed would be great since that's my usual workflow and it felt very missing here. That might be an issue if there's a partial snippet of a diff, but it seems like you might be able to set specific ranges as viewed and if that adds to the whole file, then it sets the file as viewed. Not trivial though

I was confused that the code came before the heading/explanation. It seems like the header and prose should come first, and then the code.

Makes sense, we want this too and are adjusting prompt to fix Interesting on the viewed point. Curious if you feel like you need to use "viewed" as much given the code tour is meant to be easier to read in order than a standard alphabetical listing

I think it just mainly feels weird to not be able to "viewed" a file since that's the way I've been doing code review for years lol. I think it helps since I might not always review in exact order. I'll try doing more reviews and see how that feels