code-review

Review Git diffs for requirement conformance, correctness, and project standards with ranked findings.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/oxie/prime-agent-skills --skill code-review-oxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/oxie/prime-agent-skills/tree/main/code-review
Command: npx skills add https://github.com/oxie/prime-agent-skills --skill code-review-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes consistently is hard: reviewers miss requirement gaps, conflate style preferences with real defects, or review stale snapshots. This Skill provides a disciplined, read-only review workflow that freezes the exact scope under review, separates requirement/correctness concerns from project standards, and reports only evidence-backed findings ranked by consequence. ## Core Features & Use Cases - Scoped Git review recipes: Handles branch/PR reviews, staged-only, unstaged, pre-commit, uncommitted work, and diffs since a specified commit, with trust-boundary checks before running any Git command. - Two-lens analysis: Evaluates requirement conformance and correctness separately from project standards, keeping spec evidence distinct while ranking real risks together. - Incoming feedback assessment: Evaluates review comments with accept/reject/needs-evidence/defer dispositions, including guidance for reviewer-becomes-author situations. - Use Case: Before merging a pull request, ask for a review of the branch against its merge base; receive findings with location, requirement, failure scenario, evidence, and the smallest useful fix, plus a summary of checks actually run. ## Quick Start Review the uncommitted changes in this repository for correctness and requirement coverage, and report findings without modifying any files.

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 Git branch or pull request before merging?▼

Request a review of the branch against its target; the workflow resolves both commits, computes the merge base, and diffs it against the head. Findings are ranked by consequence with location, evidence, and the smallest useful response.

How to review staged or uncommitted changes before committing?▼

Ask for a pre-commit review of current work. Staged-only requests use the index diff, unstaged requests compare the worktree to the index, and untracked files are enumerated separately with sensitive or ignored files excluded.

Can it assess incoming code review comments on my change?▼

Yes, the feedback assessment path verifies each comment against callers, tests, and platform constraints, then assigns accept, reject, needs-evidence, or defer dispositions. Implementing suggestions or publishing replies requires separate authorization.

Does the code review modify files or commit fixes automatically?▼

No, the review is read-only by default and never commits, stages, rebases, installs packages, or publishes comments. Any later fix, commit, or external publication requires its own explicit authorization.

What are the limitations of automated Git diff review?▼

A plausible implementation is not an executed result, and tooling presence is not a passing check. If project checks cannot run safely, the report states exactly what remains untested rather than certifying behavior.