code-review

Reviews pull request diffs with parallel fresh-context subagents and posts inline GitHub comments.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill code-review-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill code-review-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Self-reviewing your own code misses defects because the author already knows the intent. This Skill replaces the built-in /code-review command with a project-scoped implementation that runs independent, fresh-context reviews of PR or working-tree diffs, filters out false positives through adversarial verification, and records every finding as a line-level inline comment on the GitHub pull request. ## Core Features & Use Cases - Parallel perspective finders: Launches independent subagents per review aspect (correctness, security, simplification, tests, documentation consistency, spec fidelity, plus conditional architecture, UI accessibility, and matching-logic scopes) so each verdict is made without contamination from other concerns. - Adversarial verification: Every finding is challenged by a counter-argument agent before being confirmed, eliminating false positives and labeling uncertain items as PLAUSIBLE. - Mandatory inline review posting: Creates a pending GitHub review, attaches per-line comments with severity and recommended fixes, and submits it even when zero findings exist, so review history is always auditable. - Use Case: After opening a pull request, invoke the review to have six-plus independent perspectives examine the diff, receive confirmed defects as inline comments on exact lines, and reply or resolve each thread through the standard review flow. ## Quick Start Ask the AI to review pull request number 42 and post the findings as inline comments on GitHub.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a GitHub pull request with AI subagents?▼

Provide the PR number and the skill fetches the diff via the GitHub MCP pull_request_read method, then launches parallel independent subagents per review aspect. Confirmed findings are posted as line-level inline comments in a submitted GitHub review.

How does automated code review avoid false positives?▼

Each finding from the finder agents is passed to an adversarial verification step that attempts to disprove it by checking existing guards and reachability. Only findings that survive are marked CONFIRMED; uncertain ones are labeled PLAUSIBLE.

Can this review uncommitted working tree changes instead of a PR?▼

Yes. When no PR number is given, it diffs the current branch against origin/main including uncommitted changes. Results are reported in chat instead of inline comments since no pull request exists to attach them to.

Why does the review post a GitHub comment even with zero findings?▼

Posting an empty review distinguishes 'review performed with zero findings' from 'review never performed' when auditing PR history later. The summary records which review aspects were actually executed.

What happens when inline comment posting fails on GitHub?▼

A 422 error for out-of-hunk lines triggers one retry as a file-level comment. If that fails, findings are aggregated into a single PR issue comment, and total failure escalates to investigation rather than silent abandonment.