一键导入
diffity-tree
Open the diffity file tree browser to browse and comment on repository files
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Open the diffity file tree browser to browse and comment on repository files
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create a guided code tour that walks through the codebase to answer a question or explain a feature. Opens in the browser with step-by-step navigation and highlighted code.
Create a guided code tour that walks through the codebase to answer a question or explain a feature. Opens in the browser with step-by-step navigation and highlighted code.
Start a project-driven learning journey for any technical topic — programming languages, tools, frameworks, or concepts. Teaches through real projects, Diffity tours, and interactive conversation, adapting to the learner's pace.
Start a project-driven learning journey for any technical topic — programming languages, tools, frameworks, or concepts. Teaches through real projects, Diffity tours, and interactive conversation, adapting to the learner's pace.
Review current diff and leave comments using diffity agent commands
Review current diff and leave comments using diffity agent commands
| name | diffity-tree |
| description | Open the diffity file tree browser to browse and comment on repository files |
| user-invocable | true |
You are opening the diffity file tree browser so the user can browse repository files in the browser.
Check that {{binary}} is available: run which {{binary}}. If not found, {{install_hint}}.
Run {{binary}} tree using the Bash tool with run_in_background: true:
& or --quiet — let the Bash tool handle backgrounding.Wait 2 seconds, then run {{binary}} list --json to get the port.
Tell the user diffity tree is running. Print the URL and keep it short — don't show session IDs, hashes, or other internals. Example:
Diffity tree is running at http://localhost:5391
When you're ready:
- Leave comments on any file in your browser, then run {{slash}}resolve-tree to fix them