diff-review

Reviews git branch diffs in parallel across multiple lenses using subagents and deterministic diff collection.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill diff-review-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-review
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/diff-review
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill diff-review-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Reviewing a branch diff from a single perspective misses defects that only surface under specific viewpoints like security, concurrency, or spec compliance, and ad-hoc reviews produce inconsistent, unverifiable results. ## Core Features & Use Cases - Deterministic diff collection: A bash script gathers the review range, commit list, worktree changes, and excluded lockfiles once, then injects the same manifest into every reviewer agent. - Parallel multi-lens review: Launches one diff-reviewer subagent per lens (design, test, security, docs, performance, compat, ops, concurrency, spec, fresh-eyes) simultaneously, with per-lens reference files defining severity rules. - Consolidated severity-ranked report: Merges findings across lenses, deduplicates by file and line, and outputs must/want+/want/nit severities plus an evidence file that a pre-PR hook can gate on. - Use Case: Before opening a pull request, ask for a review of all changes since origin/main with a security lens added; the skill collects the diff, runs three reviewer agents in parallel, and writes a gate-checkable evidence file. ## Quick Start Ask the assistant to review the current branch diff against origin/main, optionally naming extra viewpoints such as security or performance.

Frequently Asked Questions about diff-review

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

FAQPage Schema
How do I review a git branch diff with multiple perspectives?

Invoke the diff-review skill with an optional base ref and lens keywords. It collects the diff once via a deterministic script, launches one reviewer subagent per lens in parallel, and merges findings into a single severity-ranked report.

What review lenses are available for code diff review?

Default lenses are design and test. Optional lenses include security (OWASP Top 10), docs, performance, compat, ops, concurrency, spec, and fresh-eyes, selectable via keywords like 'security' or 'performance' in your request.

Does the diff review skill modify or fix my code?

No. The skill is strictly read-only: it collects diffs, reviews them, and reports findings. A PreToolUse hook blocks reviewer agents from any write-capable bash commands, and fixes happen separately only after user instruction.

How does the pre-PR review gate work with diff evidence?

After each review the skill writes tasks/diff-review/evidence.md recording the HEAD commit, lenses used, and must-finding count. The pr-create hook passes only when the file exists, the commit matches current HEAD, and must count is zero.

What happens when the diff is too large to review inline?

If the cumulative diff exceeds 300 changed lines, the manifest omits the full diff and each reviewer agent fetches only the needed portions using the collect-diff script's commit, worktree, or cumulative subcommands.