diffity-review

Diffity Review Skill

You are reviewing a diff and leaving inline comments using the {{binary}} agent CLI.

Arguments

• ref (optional): Git ref to review (e.g. main..feature, HEAD~3). Defaults to working tree changes. When both ref and focus are provided, use both (e.g. /diffity-review main..feature security).
• focus (optional): Focus the review on a specific area. One of: security, performance, naming, errors, types, logic. If omitted, review everything.

CLI Reference

{{binary}} agent diff
{{binary}} agent list [--status open|resolved|dismissed] [--json]
{{binary}} agent comment --file <path> --line <n> [--end-line <n>] [--side new|old] --body "<text>"
{{binary}} agent general-comment --body "<text>"
{{binary}} agent resolve <id> [--summary "<text>"]
{{binary}} agent dismiss <id> [--reason "<text>"]
{{binary}} agent reply <id> --body "<text>"

• --file, --line, --body are required for comment
• --end-line defaults to --line (single-line comment)
• --side defaults to new
• general-comment creates a diff-level comment not tied to any file or line
• <id> accepts full UUID or 8-char prefix

Prerequisites

1. Check that {{binary}} is available: run which {{binary}}. If not found, {{install_hint}}.

Instructions

Step 1: Ensure diffity is running for the correct ref (without opening browser)

The review needs a running session whose ref matches the requested ref. A ref mismatch causes "file not in current diff" errors when adding comments.

1. Run {{binary}} list --json to get all running instances. Parse the JSON output and find the entry whose repoRoot matches the current repo.
2. If a matching entry exists, compare its ref field against the requested ref:
   • The registry stores "work" for working-tree sessions and the user-provided ref string (e.g. "main", "HEAD~3") for named refs.
   • If refs match → reuse the session, note the port, and continue to Step 2.
   • If refs don't match → restart: run {{binary}} <ref> --no-open --new (or {{binary}} --no-open --new if no ref). The --new flag kills the old session and starts a fresh one. Use Bash tool with run_in_background: true. Wait 2 seconds, then verify with {{binary}} list --json and note the port.
   • If no ref was requested and the running session's ref is not "work" → restart with {{binary}} --no-open --new (the running session is for a named ref, but we need working-tree).
3. If no session is running for this repo, start one in the background:
   • Command: {{binary}} <ref> --no-open (or {{binary}} --no-open if no ref)
   • Use Bash tool with run_in_background: true
   • Wait 2 seconds, then verify with {{binary}} list --json and note the port.