Review agent changes as a stack of small patches
At a glance
A Lobsters participant used one Pi session and Jujutsu to keep coding-agent work small enough to understand. This workflow is listed under Code review, Coding agents.
- Agents / tools
- Pi, Jujutsu (jj), Zed
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Work in a version-controlled project with Pi as the agent harness, Jujutsu for change management, and an editor for direct review. Supply concise project instructions and commit-message guidance. 2) Ask the agent to assess a design or change, and request Linux-style patches with one logical change per patch. Keep the work in one session. 3) Inspect the resulting patch stack in the editor. Edit an individual patch yourself when the design or implementation needs adjustment, rather than accepting an expanding block of unexplained code. 4) Re-review the revised patches and retain changes you understand; use the assistant to identify overlooked problems while continuing to make important design decisions yourself.
How it went
The participant reported that small patches and clear commit messages made detailed review easier.
Worth knowing
Their stated goal was understanding rather than maximum code-generation speed; they described unsupervised work as a source of trouble.