Diffity Resolve Tree
Pull open Diffity tree review threads and resolve them by applying the requested code fixes in your repo.
Overview
diffity-resolve-tree is an agent skill for the Ship phase that reads open Diffity tree comments and resolves them by making the requested code fixes.
Install
npx skills add https://github.com/kamranahmedse/diffity --skill diffity-resolve-treeWhat is this skill?
- Lists open comment threads with diffity agent list --status open --json
- Optional thread-id argument to resolve a single thread instead of the full queue
- CLI covers comment, reply, resolve with summary, and dismiss with reason
- Hard gate: requires diffity on PATH and an active tree session (diffity tree)
Adoption & trust: 542 installs on skills.sh; 687 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have review feedback scattered in Diffity tree threads and need your agent to apply fixes file-by-file without manually copying each comment.
Who is it for?
Developers already running diffity tree who want agent-driven cleanup of annotated review backlog.
Skip if: Repos with no Diffity session started, or teams that do not use Diffity for review at all.
When should I use this skill?
User invokes /diffity-resolve-tree or asks to read open Diffity tree comments and fix them; optional thread-id for one thread.
What do I get? / Deliverables
Open threads move to resolved or dismissed with code changes landed and optional resolve summaries documented in the review session.
- Code edits addressing review comments
- Resolved or dismissed Diffity threads with optional summaries
Recommended Skills
Journey fit
Ship / review is the primary home because the skill closes the loop on human or agent comments left during structured tree-based code review. Review matches listing open threads, editing files at annotated lines, and marking threads resolved or dismissed via the Diffity agent CLI.
How it compares
Diffity-session review executor—not a generic git diff skill or standalone static analyzer.
Common Questions / FAQ
Who is diffity-resolve-tree for?
Solo and small-team builders using Diffity tree who want Claude Code, Cursor, or similar agents to implement review feedback automatically.
When should I use diffity-resolve-tree?
During Ship review when open tree comments exist and you want batch or single-thread resolution after diffity tree is running.
Is diffity-resolve-tree safe to install?
The skill drives local git edits and Diffity CLI calls; review the Security Audits panel on this Prism page and treat agent file changes like any automated patch.
SKILL.md
READMESKILL.md - Diffity Resolve Tree
# 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. ## Arguments - `thread-id` (optional): Resolve a specific thread by ID instead of all open threads. Example: `/diffity-resolve-tree abc123` ## CLI Reference ``` 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 ## Prerequisites 1. Check that `diffity` is available: run `which diffity`. If not found, install it with `npm install -g diffity`. 2. 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`). ## Instructions 1. 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. 2. If there are no open threads, tell the user there's nothing to resolve. 3. 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>" ``` 4. After resolving all applicable threads, run `diffity agent list` to confirm status. 5. Tell the user to check the browser — resolved status will appear within 2 seconds via polling.