How I've changed the way I do code reviews by using the /visual-recap skill:

Source and install instructions here: Source for the MDX viewer/editor here:

I'm going to try this out and make a video about it. I talked to several people at AIE this week about building this exact skill myself, so I'm excited to play with it!

amazing @kentcdodds, if you have any Qs or issues DM me anytime, happy to help

@kentcdodds looks sweet! most def geek diving into this

@Steve8708 do i have permission to add this to my harness?

absolutely

Thank you so much

I use this same skill with some modifications for pr review also.

I changed the way I do code reviews by letting codex review claude PRs and letting claude review codex PRs 😆

*yoink

@kentcdodds This is a great way to approve a bug

This is really cool. Great work Steve.

When I get the time, I will try to use it on gitlab, since I no longer use github, unless you port it before I get to it.

is it opencode compatible?

absolutely is

you could also use code tours bias: I created it 🤭

anything that speeds up a code review is a clear win. you get to approve the deployment that takes down production with unprecedented efficiency

@plannotator

I am building something similar, but more granular control, and better experience.

Turning reviews into actual reviews instead of rubber stamps is valuable.

Is it GitHub only or can I also use it locally with any git repo when I check out the PR branch?

works anywhere - GitHub is just an example

Tried it today with the plan (it’s awesome!) but I wonder how do I do /visual-recap on a PR outside GitHub? Do I need to checkout the PR branch and it will figure out the diff from that automatically?

You still do code reviews? Our team's workflow has PR reviews mostly automated - We require a human review also, but the majority of the time it's nailing it & flagging anything important. We have a /respond the engineer can address anything that was relevant or decline points

/visual-recap catches shape, but deleted tests still need boring manual review

Do you have a YouTube channel where you explain the other skills as well? 👀

Anthropic should hire you

Will definitely give it a try seems good but, how it is different from artifacts which is launched today by claude

Try , you might change how you code with agents:)

I made a graphviz skill to show me well graphviz lol prompt in the top right corner (sorry I had to censor a bit for security - probably nothing sensitive but better safe than sorry)

@Steve8708 The MDX viewer is the useful clue. Code review shouldn’t start from a wall of comments; it should start from the changed screen/state, then jump into the diff that made it happen.

A one-size-fits-all visual recap can miss the nuance of logic errors. How do you keep the team from relying on it as a crutch instead of thinking critically?

This is the right direction. Code review is becoming less “read the diff” and more “verify the artifact.” A useful recap should include screenshots, user path, changed files, risk labels, untested cases, and rollback notes. Makes AI-assisted review auditable, not just faster.

Check out it has been a complete game changer for me.

been building something like this as well, but this is so much better, plus the MDX idea is genius! I'm playing with it right now