code-review

Reviews working-tree or branch diffs for correctness bugs and quality cleanups using parallel sub-agents.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/nsollazzo/ship-kit --skill code-review-nsollazzo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nsollazzo/ship-kit/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/nsollazzo/ship-kit --skill code-review-nsollazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing your own diff is slow and error-prone: real bugs hide among noise, and self-review misses edge cases. This Skill automates a rigorous review of the change you are currently making, catching correctness bugs and quality issues before they reach a pull request. ## Core Features & Use Cases - Parallel fan-out review: Spawns one sub-agent per review dimension (correctness, security, performance, reuse & simplification), scaled to the size of the diff, with adversarial verification that refutes each finding to eliminate false positives. - Actionable output modes: Reports findings grouped by file with severity levels, applies high-confidence fixes directly to the working tree with --fix, or posts inline PR comments via the gh CLI with --comment. - Stacked PR support: Pins the base branch explicitly (merge-base and head SHAs) so stacked diffs are compared against the correct parent, not the default branch. - Use Case: Before opening a PR, run the review on your branch diff; it flags a swallowed exception at api/handler.go:87 and an N+1 query in the new loop, then applies both fixes with --fix. ## Quick Start Ask the agent to code review my current uncommitted changes and apply the high-confidence fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review my code changes before opening a pull request?▼

Run the review on your uncommitted changes with git diff, or on a branch with git diff <base>...HEAD. The skill fans the review across correctness, security, performance, and reuse dimensions, then reports findings by file with severity and suggested fixes.

How do I automatically apply code review findings to my working tree?▼

Pass the --fix flag. After reporting, the skill applies the high-severity bug and should-fix findings as minimal, surgical edits matching surrounding style, leaving nice-to-have suggestions untouched unless trivial.

Can I post code review findings as inline comments on a GitHub PR?▼

Yes, use the --comment flag with an authenticated gh CLI. The skill resolves the PR for the current branch and posts each finding as an inline comment on the head commit via the GitHub API, falling back to printed output if gh is unavailable.

Does this code review work without sub-agent support?▼

Yes. Sub-agents are used for parallel breadth when the harness supports them, but the same review passes run sequentially without them, producing identical results. It needs only a shell with git, file reading, and editing.

How does code review handle stacked pull requests?▼

It pins the base explicitly by passing the merge-base SHA and head SHA to every reviewer, noting the branch is stacked on a parent PR rather than the default branch. This prevents findings that incorrectly flag changes belonging to the parent PR.