Flagship tool · offline
Pair programming ends. The chat closes. You're alone with a diff again. thread turns that diff into a walkthrough — summary, risk flags, per-file notes, and a review checklist. No API. No cloud.
Pure heuristics. Works on a plane, in CI, or air-gapped.
Teaches review habits — doesn't replace reading the diff.
Instant output. Pipe from git, point at a patch file.
Try it
Clone, install, run the bundled example — a real diff from the Ariadne notebook.
$ git clone https://github.com/Ariadne-Dev/thread.git
$ cd thread && pnpm install
$ pnpm dev explain --file examples/ariadne-session-3.patchOr on your own repo:
$ pnpm dev explain # unstaged changes
$ pnpm dev explain --staged # staged
$ pnpm dev explain --range main...HEAD
$ git diff HEAD~3 | pnpm dev explainExample output
Structured text you can read before diving into hunks — or paste into a PR description
with --format markdown.
Ariadne session 3 (real diff)
────────────────────────────────────────────────────────
SUMMARY
8 files changed (+256/−41). Most changes are in docs files (8). 5 new files.
RISKS
[~] Documentation updated
· README.md
· sessions/003-session-log-and-header.md
...
FILES
· sessions/003-session-log-and-header.md (docs, +53/−0) [new file]
New file with 53 lines.
· status/status.md (docs, +22/−35)
Balanced edit (+22/−35).
REVIEW CHECKLIST
☐ Read the summary and risk flags before diving into hunks.
☐ For each changed file, ask: what behavior changed?
☐ If this is a PR: would a newcomer understand *why*?How it works
Path patterns, line counts, keyword detection in hunks. Docs-only diffs won't false-alarm on prose mentioning secrets. The default path will always work offline. New to the repo? Start with trail.