Agent PRs are too big to read line by line. Kent shows a visual system recap in the PR description - classify what changed as composes, extends, or adds - so you review the architecture first, then the code that matters.

• (00:00) - Still reviewing git diffs?
• (00:25) - Spectrum: not every line, not zero review
• (00:43) - Review the system, not just the diff
• (00:51) - Steve's visual recap (Builder.io)
• (01:17) - Why I rolled my own
• (02:30) - System recap + PR #662 (adds)
• (05:08) - PR #686 (composes — low risk)
• (05:54) - Primitives playground callback
• (06:57) - Install kcd-skills visual-recap
• (07:35) - Homework + close

Better with Kent - durable skills for people who ship software.

Coding agents ship more code faster, and the review surface explodes. Some people say you have to read every line. Others say never look at the diff. The real answer is a spectrum - and the durable skill is reviewing how the system is changing, not only the syntax.

Kent walks through a visual recap approach inspired by Steve at Builder.io, then shows his own kcd-skills version that needs no account, no deploy, and no inference token. The agent that worked the PR writes a system recap block; GitHub renders the mermaid. Live demos: PR #662 adding an MCP client-servers primitive (high risk) vs PR #686 composing onboarding (low risk). Same domain, different review questions.

Homework: map your primitives, run visual recap on your next non-trivial PR, and decide whether you are reviewing an add, an extend, or a compose before you open the diff.

Links

• kcd-skills / visual-recap
• PR #662 - adds mcp-client-servers
• PR #686 - composes onboarding
• Slides deck
• Design Primitives Agents Can Actually Use
• Better with Kent