Install any skill in seconds. Free to start, no credit card required.
Get Started Free →umputun/revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos (auto-detected). Activates on "revdiff", "review diff", "review changes", "annotate diff", "git review with revdiff", "hg review with revdiff", "review jj change", "interactive diff revie
Passed 21 of 26 test cases with the skill, and 5 of 26 without it.
and 21 more in the full report
17 fixed4 passed either way4 still failing1 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
In pi, the user invokes `/skill:revdiff` and specifically asks to show only files that have not yet been marked as reviewed in the tree pane. What revdiff flag should be included?
| Checked | Without skill | With skill |
|---|---|---|
| Includes --filter-unreviewed in args. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill is specific to the pi harness. Use the revdiff pi extension for interactive review sessions.
Call the revdiff_review tool only when the user explicitly asks for revdiff, an interactive annotation pass, or captured revdiff annotations. Do not call it for ordinary autonomous requests like "review the code", "review my changes", or "review the diff"; handle those by inspecting the code directly. Do not tell the user to run /revdiff; slash commands are user-invoked only.
When the user invokes /skill:revdiff <input>, treat <input> as a request to launch revdiff unless it is clearly a usage/configuration question or an existing-history request. First figure out the concrete reference point(s) or file target the user asked for, then call revdiff_review. Do not stop after printing the resolved ref.
Reference resolution rules:
in ~/source/repo), use that directory for any git/ref/path resolution, omit that directory phrase from the revdiff args, and pass the directory as the revdiff_review tool's cwd parameter.prev commit, previous commit, last commit → HEAD~1 HEAD; head-3, head 3, previous 3 commits, last 3 commits → HEAD~3 HEAD.last tag or latest tag → run git describe --tags --abbrev=0, then pass that tag as args.2 weeks ago, yesterday, last Friday → run git rev-list -1 --before=<phrase> HEAD, then pass the resulting commit hash as args.args: "--only <path>".all files exclude vendor and dist → args: "--all-files --exclude=vendor --exclude=dist".Tool examples:
/revdiffargs: "main": review the current branch against mainargs: "--staged": review staged changesargs: "--untracked": review untracked files with working-tree changesargs: "--only README.md": review one standalone fileargs: "--all-files --exclude vendor": review all tracked files except vendorargs: "--no-tree": review with the file tree pane hiddenargs: "--filter-unreviewed": show only files not marked reviewedargs: "--page-overlap=2": keep 2 lines from the previous screen when pagingargs: "--start-at-change": position the cursor on the first changed lineargs: "--cross-file-motion": let cursor motion continue into adjacent filesargs: "--description='why this refactor matters' main": include review context in the info popupargs: "--description-file=/tmp/revdiff-desc.md main": include longer markdown review contextargs: "--annotations=/tmp/revdiff-review.md main": preload in-session review notesargs: "main", cwd: "~/source/repo": run revdiff from a specific working directory when the session was started elsewhere.test cases passed, vs 5 / 26 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.