hunk-review

Navigate Hunk terminal diff sessions and place inline review comments.

Updated Jul 2, 2025
One-click install
npx skills add https://github.com/janpeterd/dotfiles --skill hunk-review-janpeterd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunk-review
Source: https://github.com/janpeterd/dotfiles/tree/main/dot_agents/skills/hunk-review
Command: npx skills add https://github.com/janpeterd/dotfiles --skill hunk-review-janpeterd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you inspect and review code changes inside a live Hunk terminal session without breaking the interactive workflow or guessing which file/hunk is currently focused.

Core Features & Use Cases

  • Live session inspection: Lists sessions and fetches repo/path/source context plus hunk and file structure via JSON for accurate targeting.
  • Precise navigation: Moves the Hunk TUI to specific files and hunks, or jumps between previously added comments.
  • Reload and iterate safely: Reloads the currently open session contents by swapping the underlying review command (e.g., switching branches/refs or diff ranges).
  • Inline review comments: Adds one-off comments or applies batches from JSON stdin to multiple locations with optional focus behavior.

Quick Start

Tell your AI to locate the current Hunk session for your worktree, align the view to the relevant file/hunk, reload if necessary, and add an inline review comment at the right new-line or old-line target.

Frequently Asked Questions about hunk-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I leave inline comments on specific git diff hunks in a terminal UI?

To leave inline comments on git diff hunks in a terminal UI, you can use an interactive review session to navigate to specific files and hunks, then place comments at exact new-line or old-line targets without losing your diff context.

Can I reload a git diff range in an interactive terminal session without losing my place?

Yes, you can reload a git diff range in an interactive terminal session by swapping the underlying review command, such as switching branches or refs, which updates the session contents while maintaining your navigation state.

How do I ensure inline code review comments target the correct file and hunk context?

To ensure inline code review comments target the correct context, fetch the repo, path, and hunk structure via JSON inspection first, then use line-precise navigation commands to align the terminal focus before adding comments.

Can I batch add code review comments to multiple diff locations from JSON input?

Yes, you can batch add code review comments to multiple diff locations by applying them from JSON stdin, allowing targeted placement across various hunks with optional focus behavior to jump between them.

What is the best way to navigate between previously added comments during a terminal code review?

The best way to navigate between previously added comments during a terminal code review is to use hunk session commands that jump directly between commented locations, ensuring you review existing feedback without scrolling through the entire diff.

Do I need to manually find my worktree session before reviewing git diffs?

No, you do not need to manually find your worktree session, as the review workflow can locate the current live terminal session for your worktree automatically, fetch its context, and align the view to the relevant file and hunk.