hunk-review

Coordinate local code review sessions with Hunk daemon lifecycle management.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/tuliof/dindin --skill hunk-review-tuliof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunk-review
Source: https://github.com/tuliof/dindin/tree/main/.agents/skills/hunk-review
Command: npx skills add https://github.com/tuliof/dindin --skill hunk-review-tuliof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of coordinating asynchronous code reviews between implementation and review agents by providing a standardized, local-first workspace that ensures source identity and review integrity.

Core Features & Use Cases

  • Session Lifecycle Management: Orchestrates the daemon and review session lifecycle to ensure consistent, isolated review environments.
  • Source Identity Verification: Enforces strict validation of worktree paths, branches, and commit hashes to prevent review mismatches.
  • Conventional Commenting: Facilitates structured, actionable feedback using standardized prefixes like issue, suggestion, and question.
  • Use Case: A Scrum Master uses this skill to hand off an implementation branch to a QA agent, ensuring the reviewer inspects the exact same worktree state without manual checkout errors.

Quick Start

Initiate a new hunk review session by providing the implementation worktree path and the specific branch name to the agent.

Frequently Asked Questions about hunk-review

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

FAQPage Schema
How do I automate code review between agents without manual git checkout?

Automated code review between agents is managed by coordinating local daemon lifecycles and verifying worktree paths, branches, and commit hashes. This enforces read-only safety for the implementation worktree and maintains a persistent review audit trail.

What are conventional comments in an automated code review workflow?

Conventional comments in an automated code review workflow are structured feedback exchanges using standardized prefixes like issue, suggestion, and question. This format facilitates actionable feedback between agents without requiring manual repository manipulation.

How do I ensure source identity verification during an asynchronous code review?

Source identity verification during an asynchronous code review is enforced by strictly validating worktree paths, branches, and commit hashes. This prevents review mismatches and ensures the reviewer inspects the exact same worktree state.

Can I use a local-first workspace to hand off an implementation branch to a QA agent?

Yes, you can use a local-first workspace to hand off an implementation branch to a QA agent. The session lifecycle management orchestrates isolated review environments, ensuring the reviewer inspects the exact state without manual checkout errors.

Does the hunk-review skill support isolated review environments for multiple agents?

The hunk-review skill supports isolated review environments by orchestrating daemon and review session lifecycles. It ensures consistent, isolated environments for asynchronous code reviews between implementation and review agents.

What are the limitations of coordinating asynchronous code reviews locally?

Coordinating asynchronous code reviews locally requires strict validation of worktree paths and commit hashes to prevent mismatches. The implementation worktree is maintained in a read-only state, limiting direct modifications during the review session.