katamari: Skill for Claude Code

Addressing katamari review comments

katamari (ktmr) is a terminal diff-review tool. A human reviewer reads your diff inside ktmr diff, leaves comments anchored to specific file/line positions, and expects you to address each one and mark it resolved — this skill is that workflow.

Workflow

1. List the open comments:

   ktmr comments list --json
   

   Each line is one JSON object:

   {"id": "a1b2c3d4", "created_at": 1700000000, "file": "src/lib.rs",
    "anchor": {"new_line": 42, "content_hash": ..., "context_hash": ...},
    "body": "this should handle the empty-input case too",
    "status": "open"}
   

   file is repo-relative; anchor.new_line is the 1-based line in the working tree version of that file at the moment the comment was written. Open the file and read that line (and its surroundings) to see what the comment is about — if the file has changed a lot since, the line number may no longer point at exactly the right spot; use judgment and the comment's own wording rather than trusting the number blindly. (katamari's own UI relocates comments live as the file changes; this CLI output always reports the comment's last known anchor.)

   A comment can also cover a contiguous range instead of one line: when that's the case, the object also has an end_anchor with the same shape as anchor, and the two together mean "every line from anchor.new_line to end_anchor.new_line, inclusive." Treat the comment as being about that whole range — read and address every line in it, not just the first one.

2. For each open comment, make the requested change in the working tree.

3. Mark it resolved:

   ktmr comments resolve <id>
   

   The reviewer's ktmr diff session picks this up live — no restart needed — and shows the comment as resolved (dimmed, struck through) at its current position in the diff.

4. If a comment doesn't apply (already fixed, or you disagree with it), still resolve it rather than leaving it open silently, and say why in your own summary back to the reviewer.