Local code review at AI speed.
Your AI writes faster than you can review. Tour lets your AI leave a walkthrough on its diff as PR-style comments. Reply to the agent's comments, add your own, and jump to your editor in one keystroke.
Homebrew (macOS, Linux):
brew install a9a4k/tap/tournpm:
npm i -g tourdiffOr any other Node package manager: pnpm add -g tourdiff · bun add -g tourdiff · yarn global add tourdiff.
Verify:
tour --versionTeach your AI agent (Claude Code, Codex, Cursor, Gemini CLI, OpenCode, …) how to leave Tours when you ask for a review:
npx skills add a9a4k/tour -gNow asking your agent to "review this branch" or "walk me through this diff" produces a Tour — line-anchored comments, opened in your browser at a clickable URL — instead of a wall of chat. Works across the skills.sh ecosystem.
Run tour init to have Tour write a commented template to ~/.tour/config.toml (or $TOUR_HOME/config.toml):
tour initUncomment your agent and editor in ~/.tour/config.toml:
# Spawned when you "Request Reply" on a comment — the AI that replies.
reply_agent = "claude --print --allowedTools Read,Grep,Glob,Bash --system-prompt {systemPrompt} {userPrompt}"
# Spawned when you press `o` on a line — your editor.
editor = "code -g {file}:{line}" # VSCode
# editor = "cursor -g {file}:{line}" # Cursor
# editor = "idea --line {line} {file}" # JetBrains
# editor = "vim +{line} {file}" # vim{systemPrompt} / {userPrompt} are placeholders Tour fills in at spawn time. {file} and {line} come from the focused comment's anchor.
Verify:
tour config showShould print both fields with (from config) as the source.
Talk to your AI agent in plain English. Three patterns that produce good tours:
"Create a tour for my uncommitted changes."
Snapshots the working tree as a synthetic pinned commit and walks you through it. No git commit needed first.
"Create a tour for this PR."
Tours the diff between your branch and its merge base. Works on any branch — no PR needs to exist on GitHub yet.
"For each subtask, leave its own tour. Keep the diff isolated to one subtask."
A convention to set up front in multi-step sessions. One tour per logical change beats one fat tour at the end — comments stay anchored to the diff they're reasoning about, and the reply loop has less to wade through.
"Pick up the tour comments and let's discuss."
Brings the agent's walkthrough plus any replies you left back into your current session. Useful for continuing a review thread that started yesterday, or carrying tour-side decisions back into code edits.
tour init # seed ~/.tour/config.toml
tour config show # show resolved config + sources
tour create --head <ref> [--base <ref>] [--title <s>] [--force] [--json]
tour comment <id> --file <f> --side additions|deletions --line <n[-m]> --body <b> [--json]
tour comment <id> --reply-to <comment-id> --body <b> [--json] # reply on a thread
tour comment <id> --edit <comment-id> --body <b> [--as-human] [--json] # edit (humans only)
tour comment <id> --delete <comment-id> [--json] # delete a comment
tour comment <id> --batch - # read JSONL from stdin (alias: annotate)
tour list [--all] [--status open|closed|all] [--json]
tour show <id> [--json]
tour pickup <id> [--json] # agent consumes human replies on this tour
tour # open the best surface for the env
tour tui [<id>] [--reply-agent <template>] [--editor <cmd>]
tour serve [--port 8687] [--open] [<id>] [--reply-agent <template>] [--editor <cmd>]
tour close <id> # mark closed; keeps files
tour delete <id> # remove the tour
tour prune --older-than <duration> # bulk-delete by age
--head WIP snapshots uncommitted work to a synthetic commit so the diff stays pinned. Full reference: tour --help.
MIT — see LICENSE.