为什么值得关注

它提供了一种基于会话的持续审查工作流，将审查与模型上下文解耦，允许代理继续工作，同时用户可以使用内联评论和两种差异模式审查增量更改。

适合谁使用

需要在交互式会话期间审查增量更改的 pi 代理用户
在 Git 仓库中使用 pi 并希望获得持久审查界面的开发者
使用 pi 进行代码生成并需要结构化审查循环而不会丢失上下文的团队

典型使用场景

审查并评论 pi 代理生成的一批更改，然后再提交
跟踪上次审查检查点与当前工作区之间的差异，仅查看新更改
将完整工作树与 HEAD 进行比较，同时保留单独的检查点用于增量审查

项目优势

持久的审查窗口，随着文件更改而递增更新
基于检查点的审查状态，可通过 pi 会话保存和恢复
两种差异模式（自上次审查起 vs 与 HEAD 比较）以及双面板内联评论
无需解析工具调用即可处理任何磁盘变更（代理、用户或外部工具）

使用前须知

需要 pi、Git 仓库和 Node.js 20+，不是独立工具
检查点自定义条目不参与模型上下文，AI 无法看到审查注释
审查窗口会在 pi 关闭、切换会话或扩展重载时关闭，需要手动重新打开

README 快速开始

Review Loop

A persistent, incremental diff reviewer for pi.

Review Loop keeps a native review window open while the agent works. Submitting a review records the current workspace as a session-backed checkpoint, so the next review can show only the changes made afterward.

Install

pi install git:github.com/earendil-works/pi-review-loop

Update an existing installation with:

pi update --extensions

Start pi in a Git repository and open the reviewer:

/diff-review

The command returns immediately; it does not replace pi's editor. Running /diff-review again brings the existing review window forward.

Review workflow

Open the window with /diff-review.
Select a file from Recently Changed or the Files tree.
Review its diff.
Hover a line number to reveal a +, then click it to add an inline comment.
- The left pane refers to Reviewed content in Since review mode or HEAD in vs HEAD mode.
- The right pane refers to the Current on-disk content.
- Inline comments work on either pane.
Use Add file note for feedback that is not tied to a line.
Comment-count badges appear beside files in both sidebar sections.
Click the review button in the top-right.
- All files currently changed since the checkpoint are marked reviewed, whether or not each file was opened.
- The current workspace becomes the new review checkpoint.
- Review feedback is inserted into pi's normal editor.
- Feedback is not sent automatically; inspect or edit it in pi, then submit it normally.
Keep the window open. Later changes appear as the next review batch.

Submitting with no comments simply marks the current workspace as reviewed.

Diff modes

Since review

Compares:

last review checkpoint → current workspace

This is the default review queue. After submitting a review, it becomes empty until files change again.

Before the first checkpoint, the baseline is the HEAD captured when Review Loop opens.

vs HEAD

Compares:

current HEAD → current workspace

This shows the complete current working-tree change set, including changes already covered by a review checkpoint. Files that still match the last checkpoint display a green reviewed checkmark; files changed afterward retain the blue pending indicator.

Changing modes does no

项目描述

A persistent incremental diff review loop for pi

pi-review-loop