// Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files and hunks, reloads session contents, and adds inline review comments. Use when the user has a Hunk session running or wants to review diffs interactively.
Apple-authored SwiftUI and platform guidance extracted from Xcode. Helps AI agents write idiomatic, Apple-native SwiftUI with reduced hallucinations.
Apple-authored SwiftUI and platform guidance extracted from Xcode. Helps AI agents write idiomatic, Apple-native SwiftUI with reduced hallucinations.
Ensure files are re-read before editing to avoid overwriting user changes. Use only when explicitly encouraged to by user.
Enforce Bare-style builtin imports and package-local import maps for Holepunch, Pear, Autobonk, Bare runtime, and other dual-runtime JavaScript work. Use when editing code that may run under Bare or a repo that already uses package.json "imports" for bare polyfills. Prefer plain builtin specifiers like "fs", "path", "crypto", "url", "http", and "https" instead of "node:*", and update the nearest package.json import map and dependencies when a new builtin is introduced.
Render Mermaid diagrams as SVG and PNG using the Beautiful Mermaid library. Use when the user asks to render a Mermaid diagram.
Write git commit messages. Use when asked to commit, write a commit message, or stage and commit changes.
| name | hunk-review |
| description | Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files and hunks, reloads session contents, and adds inline review comments. Use when the user has a Hunk session running or wants to review diffs interactively. |
Hunk is an interactive terminal diff viewer. The TUI is for the user -- do NOT run hunk diff, hunk show, or other interactive commands directly. Use hunk session * CLI commands to inspect and control live sessions through the local daemon.
If no session exists, ask the user to launch Hunk in their terminal first.
1. hunk session list # find live sessions
2. hunk session get --repo . # inspect path / repo / source
3. hunk session review --repo . --json # inspect file/hunk structure first
4. hunk session review --repo . --include-patch --json # opt into raw diff text only when needed
5. hunk session context --repo . # check current focus when needed
6. hunk session navigate ... # move to the right place
7. hunk session reload -- <command> # swap contents if needed
8. hunk session comment add ... # leave one review note
9. hunk session comment apply ... # apply many agent notes in one stdin batch
Most session commands accept:
--repo <path> -- match the live session by its current loaded repo root (most common)<session-id> -- match by exact ID (use when multiple sessions share a repo)reload also supports:
--session-path <path> -- match the live Hunk window by its current working directory--source <path> -- load the replacement diff / show command from a different directoryUse --source only for advanced reloads where the live session you want to control is not already associated with the checkout you want to load next. For a normal worktree session, prefer selecting it directly with --repo /path/to/worktree.
hunk session list [--json]
hunk session get (--repo . | <id>) [--json]
hunk session context (--repo . | <id>) [--json]
hunk session review (--repo . | <id>) [--json] [--include-patch]
get shows the session Path, Repo, and Source, which helps when choosing between --repo and --session-pathRepo is what --repo matches; Path is what --session-path matchesreview --json returns file and hunk structure by default; add --include-patch only when a caller truly needs raw unified diff textAbsolute navigation requires --file and exactly one of --hunk, --new-line, or --old-line:
hunk session navigate --repo . --file src/App.tsx --hunk 2
hunk session navigate --repo . --file src/App.tsx --new-line 372
hunk session navigate --repo . --file src/App.tsx --old-line 355
Relative comment navigation jumps between annotated hunks and does not require --file:
hunk session navigate --repo . --next-comment
hunk session navigate --repo . --prev-comment
--hunk <n> is 1-based--new-line / --old-line are 1-based line numbers on that diff side--next-comment or --prev-comment, not bothSwaps the live session's contents. Pass a Hunk review command after --:
hunk session reload --repo . -- diff
hunk session reload --repo . -- diff main...feature -- src/ui
hunk session reload --repo . -- show HEAD~1
hunk session reload --repo . -- show HEAD~1 -- README.md
hunk session reload --repo /path/to/worktree -- diff
hunk session reload --session-path /path/to/live-window --source /path/to/other-checkout -- diff
-- before the nested Hunk command--repo or <session-id> usually selects the session you want--source is advanced: it does not select the session; it only changes where the replacement review command runshunk session reload --repo /path/to/worktree -- diff--session-path targets the live window when you need to keep session selection separate from reload sourcehunk session comment add --repo . --file README.md --new-line 103 --summary "Tighten this wording" [--rationale "..."] [--author "agent"] [--focus]
printf '%s\n' '{"comments":[{"filePath":"README.md","newLine":103,"summary":"Tighten this wording"}]}' | hunk session comment apply --repo . --stdin [--focus]
hunk session comment list --repo . [--file README.md]
hunk session comment rm --repo . <comment-id>
hunk session comment clear --repo . --yes [--file README.md]
comment add is best for one note; comment apply is best when an agent already has several notes readycomment add requires --file, --summary, and exactly one of --old-line or --new-linecomment apply payload items require filePath, summary, and exactly one target such as hunk, hunkNumber, oldLine, or newLinecomment apply reads a JSON batch from stdin and validates the full batch before mutating the live session--focus when you want to jump to the new note or the first note in a batchcomment list and comment clear accept optional --file--summary and --rationale defensively in the shellhunk diff includes untracked files by default. If the user wants tracked changes only, reload with --exclude-untracked:
hunk session reload --repo . -- diff --exclude-untracked
The user may ask you to walk them through a changeset or review code using Hunk. Start with hunk session review --json to understand the file/hunk structure without inflating agent context, then use --include-patch only for the files you truly need to read in raw diff form. Use context and navigate to line up the user's current view before adding comments.
Your role is to narrate: steer the user's view to what matters and leave comments that explain what they're looking at.
Typical flow:
reload if needed)comment apply batch over many separate shell invocationsGuidelines:
comment apply for agent-generated batches and comment add for one-off notes--focus sparingly when the note itself should actively steer the reviewcontext, then reload if needed.<session-id> explicitly.Path via hunk session get or list, then use --session-path.--" -- include -- before the nested diff / show command.comment apply only reads its batch payload from stdin.--hunk, --old-line, or --new-line.