review

Review git diffs for UX, visual, accessibility, security, and constitution violations.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/bernajaber/pi-product-system --skill review-bernajaber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/bernajaber/pi-product-system/tree/main/skills/review
Command: npx skills add https://github.com/bernajaber/pi-product-system --skill review-bernajaber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It detects human-facing quality issues that automated tests cannot catch, including UX regressions, visual defects, accessibility gaps, and product-constitution violations, preventing problematic code from reaching users.

Core Features & Use Cases

  • Read the branch diff against the base branch and evaluate changes file-by-file using a severity rubric (P0–P3).
  • Identify and require fixes for blocking and urgent issues (P0/P1) and report P2/P3 code-quality suggestions for maintainers.
  • Use case: run during the review phase of a pull request to ensure UI, accessibility, and product-guideline compliance before publishing.

Quick Start

Run the review skill to analyze the current branch diff and produce a prioritized list of P0–P3 findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch UX and accessibility issues in a pull request before release?

To catch UX and accessibility issues before release, run a self-review on your committed code to evaluate pull request diffs against a P0–P3 severity rubric, enforcing fixes for blocking P0 and P1 problems.

What visual and product-constitution violations can a code review detect?

A code review detects human-facing visual defects, UX regressions, accessibility gaps, and product-constitution violations by reading the git diff against the base branch and reporting findings with P0–P3 severities.

How do I review a git diff for accessibility and UX regressions?

Review a git diff for accessibility and UX regressions by analyzing the branch changes file-by-file, identifying urgent P0 and P1 issues that require fixes, and reporting P2 and P3 code-quality suggestions for maintainers.

Can I run an automated UX review after my code passes automated tests?

Yes, you can run a UX review after code passes automated tests. It specifically focuses on human-facing UI issues and UX flows that automated tests cannot catch, evaluating the pull request diff against the base branch.

What is the best way to enforce fixes for blocking UI issues in a pull request?

The best way to enforce fixes for blocking UI issues is to apply a severity rubric during the review phase, requiring fixes for P0 and P1 violations before release while documenting P2 and P3 suggestions.

Does this code review approach work for security and product-constitution compliance?

Yes, this code review works for security and product-constitution compliance by evaluating the committed branch diff to identify violations, categorizing findings from P0 to P3, and enforcing fixes for blocking and urgent issues.