diffity-resolve-tree

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Diffity Resolve Tree Skill

You are reading open comments left on repository files via the

diffity tree

browser and resolving them by making the requested code changes.

你正在通过

diffity tree

浏览器查看仓库文件上留下的未处理评论，并通过执行要求的代码变更来解决这些评论。

Arguments

参数

```
thread-id
```
(optional): Resolve a specific thread by ID instead of all open threads. Example:
```
/diffity-resolve-tree abc123
```

```
thread-id
```
（可选）：通过ID解决特定的评论线程，而非所有未处理线程。示例：
```
/diffity-resolve-tree abc123
```

CLI Reference

CLI参考

diffity agent list [--status open|resolved|dismissed] [--json]
diffity agent comment --file <path> --line <n> [--end-line <n>] --body "<text>"
diffity agent resolve <id> [--summary "<text>"]
diffity agent dismiss <id> [--reason "<text>"]
diffity agent reply <id> --body "<text>"

```
--file
```
,
```
--line
```
,
```
--body
```
are required for
```
comment
```
```
--end-line
```
defaults to
```
--line
```
(single-line comment)
```
<id>
```
accepts full UUID or 8-char prefix

diffity agent list [--status open|resolved|dismissed] [--json]
diffity agent comment --file <path> --line <n> [--end-line <n>] --body "<text>"
diffity agent resolve <id> [--summary "<text>"]
diffity agent dismiss <id> [--reason "<text>"]
diffity agent reply <id> --body "<text>"

```
--file
```
、
```
--line
```
、
```
--body
```
是
```
comment
```
命令的必填项
```
--end-line
```
默认值为
```
--line
```
（即单行评论）
```
<id>
```
支持完整UUID或8字符前缀

Prerequisites

前置条件

Check that
```
diffity
```
is available: run
```
which diffity
```
. If not found, install it with
```
npm install -g diffity
```
.
Check that a tree session exists: run
```
diffity agent list
```
. If this fails with "No active review session", tell the user to start diffity tree first (e.g.
```
diffity tree
```
).

检查
```
diffity
```
是否可用：执行
```
which diffity
```
。如果未找到，通过
```
npm install -g diffity
```
进行安装。
检查是否存在树状会话：执行
```
diffity agent list
```
。如果执行失败并提示“No active review session”，请告知用户先启动diffity tree（例如：
```
diffity tree
```
）。

Instructions

操作步骤

List open comment threads with full details:
```
diffity agent list --status open --json
```
If a
```
thread-id
```
argument was provided, filter to just that thread. The JSON output includes the full comment body, file path, line numbers, and side for each thread.
If there are no open threads, tell the user there's nothing to resolve.
For each open thread: a. Skip general comments (filePath
```
__general__
```
) — these are summaries, not actionable code changes. b. Skip threads where the last comment is an agent reply that asks the user a question and the user hasn't responded yet — the agent is waiting for user input. c. [question]
comments (from the user) — read the question, examine the relevant code, and reply with an answer:
```
diffity agent reply <thread-id> --body "Your answer here"
```
Then resolve the thread with a summary of your answer. d. Comments phrased as questions without an explicit
```
[question]
```
tag (e.g. "should we add X?" or "can we rename this?") are suggestions — treat them as actionable requests and make the change. e. Read the comment body from the JSON output and understand what change is requested. The comment is anchored to a specific file and line range — read the full file to understand context:
- If the comment suggests a code change, refactor, or improvement, make the change.
- If the comment suggests adding documentation, add or update the relevant docs.
- If the comment is genuinely unclear, reply asking for clarification:
```
diffity agent reply <thread-id> --body "Could you clarify what change you'd like here?"
```
f. After making the change, resolve the thread with a summary:
```
diffity agent resolve <thread-id> --summary "Fixed: <brief description of what was changed>"
```
After resolving all applicable threads, run
```
diffity agent list
```
to confirm status.
Tell the user to check the browser — resolved status will appear within 2 seconds via polling.

查看包含完整详情的未处理评论线程：
```
diffity agent list --status open --json
```
如果提供了
```
thread-id
```
参数，则仅筛选该线程。JSON输出包含每个线程的完整评论内容、文件路径、行号和侧边信息。
如果没有未处理线程，告知用户没有需要解决的内容。
对于每个未处理线程： a. 跳过通用评论（文件路径为
```
__general__
```
）——这些是摘要，而非可执行的代码变更请求。 b. 跳过最后一条评论是Agent回复且正在等待用户回应的线程——Agent正在等待用户输入。 c. [question]
类型评论（来自用户）——阅读问题，检查相关代码，然后回复答案：
```
diffity agent reply <thread-id> --body "你的答案在这里"
```
然后使用你的答案摘要来解决该线程。 d. 未带有明确
```
[question]
```
标签的疑问式评论（例如“我们应该添加X吗？”或“我们可以重命名这个吗？”）视为建议——将其作为可执行请求并进行变更。 e. 从JSON输出中读取评论内容，理解所需的变更。评论锚定到特定文件和行范围——阅读完整文件以了解上下文：
- 如果评论建议代码变更、重构或改进，执行相应变更。
- 如果评论建议添加文档，添加或更新相关文档。
- 如果评论内容确实不明确，回复请求澄清：
```
diffity agent reply <thread-id> --body "你能说明一下这里需要什么变更吗？"
```
f. 完成变更后，使用摘要解决该线程：
```
diffity agent resolve <thread-id> --summary "已修复：<变更内容的简短描述>"
```
解决所有适用线程后，执行
```
diffity agent list
```
确认状态。
告知用户查看浏览器——通过轮询，已解决状态将在2秒内显示。