review

Review a local diff or supplied patch against requirements and return severity-categorized findings.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill review-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sandsower/beislid/tree/main/skills/review
Command: npx skills add https://github.com/sandsower/beislid --skill review-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often reach pull requests without a structured, requirements-grounded review, letting correctness bugs, missing tests, and security risks slip through. This Skill provides a side-effect-free review primitive that inspects a diff and returns categorized findings with a readiness verdict. ## Core Features & Use Cases - Severity-Categorized Findings: Classifies issues as Critical, Important, or Minor, each with file/line evidence, confidence level, suggested fix, and verification suggestion. - Requirements-Grounded Review: Loads specs, design docs, and ticket context so the diff is judged against actual requirements rather than generic style. - Reusable Review Contract: A fixed output format that other workflows (ready-for-review, fresh-eyes, rinse, pr-patrol) can consume, plus a prompt template for external reviewers. - Use Case: Before opening a PR, ask for a review of your local diff against the base branch; you receive blocking findings, optional improvements, and a merge-readiness verdict without any files being edited or comments posted. ## Quick Start Review my current local diff against the main branch and give me severity-categorized findings with a readiness verdict.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a local git diff before creating a pull request?▼

Run the review skill on your local diff against the base branch. It computes the merge-base, inspects the diff, and returns findings grouped by Critical, Important, and Minor severity with a merge-readiness verdict.

How to review code changes against requirements or a spec?▼

The review skill loads context from design docs, spec files, and ticket summaries, then checks the diff for requirements fit and scope creep. If no requirements exist, it reviews against general production readiness and says so.

Can the review skill fix the issues it finds?▼

No. Review is a side-effect-free primitive that only returns findings with suggested fixes. Callers such as rinse or the user decide whether and how to apply fixes, then may rerun review to verify.

What is the difference between review and fresh-eyes?▼

Review handles standard diff inspection against requirements, while fresh-eyes performs a final whole-diff pass after iterative fixes, focusing on cross-file consistency, config drift, and stale docs. Review can be reused by fresh-eyes but defers to it for that posture.

Does the review skill post comments on GitHub pull requests?▼

No. Review never posts comments, edits files, commits, or pushes. The pr-patrol workflow may call this review contract on remote PR diffs and handle comment posting separately after user approval.