review

Review diffs against fixed points for standards, spec, and risk compliance.

3|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill review-malinskibeniamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/malinskibeniamin/skills/tree/main/review
Command: npx skills add https://github.com/malinskibeniamin/skills --skill review-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a diff from a fixed point across Standards, Spec, and risk gates to guide PR reviews and ensure governance before merging.

Core Features & Use Cases

  • Provides a structured, multi-hat review workflow across Standards and Spec, with risk-gate checks.
  • Helps teams review branches, PRs, or WIP changes by outlining required verifications and evidence.
  • Use Case: when validating a new PR, run a diff review to align with project standards and risk gates.

Quick Start

Provide a diff review against a fixed point to verify Standards, Spec, and risk gates before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a diff against project standards and spec before merging a PR?

Diff review against a fixed point identifies changes between a baseline and HEAD, then checks them against Standards and Spec sources to report risk-gated findings and suggested fixes before merging.

What is a diff-driven review and how does it guide PR governance?

Diff-driven review evaluates branch changes from a fixed point across Standards, Spec, and risk gates to guide PR reviews and ensure governance before merging by outlining required verifications and evidence.

How do I check if my WIP branch changes pass risk gates and comply with standards?

You can check WIP branch changes by running a diff review against a fixed point to align with project standards and risk gates, which verifies compliance and reports findings with suggested fixes.

Does this diff review approach work without external dependencies or components?

Yes, the diff review approach works without external dependencies or components, relying solely on identifying the diff between a fixed point and HEAD to verify compliance against Standards, Spec, and risk gates.

What's the best way to structure a multi-hat code review for a new PR?

The best way to structure a multi-hat code review is to use a structured workflow across Standards and Spec with risk-gate checks, validating the PR diff against a fixed point to outline required verifications and evidence.

When should I avoid using a fixed point diff review for branch validation?

You should avoid using a fixed point diff review when you cannot establish a clear baseline point or when your project lacks defined Standards and Spec sources required to verify compliance and report gated risk findings.