Skill Detail

Review agent-authored diffs with Hunk

Use Hunk to keep a live terminal review UI open for agent-authored code changes, with Git, Jujutsu, Sapling, patch input, watch mode, and inline agent annotations.

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Security Reviewed
โญ 6.9k GitHub stars โฌ‡ 12.9k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill review-agent-authored-diffs-with-hunk Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Hunk CLI, Git/Jujutsu/Sapling or patch input, Node.js 18+ for npm install or Homebrew, optional coding-agent access to the Hunk skill path
Install & setup
Install with npm i -g hunkdiff or brew install hunk, open a review with hunk diff, hunk diff –watch, hunk show, or hunk patch -, then run hunk skill path and ask the coding agent to load that skill for live review annotations.
Author
Hunk contributors
Publisher
Open Source
Last updated
Jul 15, 2026
Quick brief

Use Hunk when an operator needs to review an AI coding agent’s changes as they evolve instead of reading raw git diff output or waiting for a pull request. The agent/operator opens Hunk against a working tree, commit, revset, file pair, or patch stream, enables watch mode when useful, and lets the coding agent load Hunk’s skill so comments and annotations appear beside the relevant code. Invoke it instead of a normal diff viewer when a review session needs multi-file navigation, live reloads, inline AI or agent notes, and a repeatable human-in-the-loop review lane. The scope boundary is the review workflow for agent-authored changesets; it is not a generic terminal UI, Git wrapper, or code-hosting replacement.

How it works

What this skill actually does

Inputs and prerequisites: Hunk CLI, Git/Jujutsu/Sapling or patch input, Node.js 18+ for npm install or Homebrew, optional coding-agent access to the Hunk skill path.

Setup notes: Install with npm i -g hunkdiff or brew install hunk, open a review with hunk diff, hunk diff –watch, hunk show, or hunk patch -, then run hunk skill path and ask the coding agent to load that skill for live review annotations.

Source and verification boundary: use https://hunk.dev as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.