review

Review local code diffs with targeted quality and formatting checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Jeqqe/jersal-project-template --skill review-jeqqe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/review
Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill review-jeqqe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps you review local code changes safely and efficiently by turning a raw diff into a structured, high-confidence review with targeted checks.

Core Features & Use Cases

  • Diff-first review: Determines what changed and what to inspect from the workspace diff output.
  • Context-aware quality checks: Runs the skill’s helper scripts to verify quality and formatting, with an option to skip slow builds.
  • Risk-reducing review passes: Applies review passes across correctness, architecture, state/data flow, routing, security, accessibility, PWA/offline behavior, and testing, prioritizing blocking issues only.
  • Local-only reporting: Produces findings for conversation without posting back to GitHub.

Quick Start

Use the review skill when you want to review local changes without a GitHub PR number, for example by asking: " /skill:review — please review my local changes and tell me what to fix 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 local code changes before creating a pull request?

Review local code changes by analyzing workspace diffs, reading relevant context, inspecting changed files, and running targeted quality checks. This process surfaces high-confidence issues across architecture, security, and accessibility, providing structured reviewer output to fix problems before merging.

What does a local diff review cover for PWA and offline behavior?

A local diff review covers PWA and offline behavior by inspecting workspace changes across architecture, state/data flow, routing, components, and accessibility. It runs targeted quality and formatting checks to identify high-confidence issues and classify their severity for structured output.

Can I run code review checks without waiting for slow CI builds?

Yes, you can run targeted quality and formatting checks while skipping slow builds by using the SKIP_BUILD option. This allows the local review process to analyze diffs and surface high-confidence issues across security, architecture, and accessibility without waiting for full builds.

How do code review passes classify severity for local workspace changes?

Code review passes classify severity by applying focused checks across correctness, architecture, state/data flow, routing, security, accessibility, PWA, and testing. They prioritize blocking issues only, ensuring the structured reviewer output surfaces exclusively high-confidence findings from the local diff.

Does the local code review post findings back to GitHub?

No, the local code review does not post findings back to GitHub. It produces local-only reporting for the conversation, generating structured reviewer output from the workspace diff analysis without interacting with remote pull requests or external platforms.

What is the best way to check security and accessibility in local diffs?

The best way to check security and accessibility in local diffs is by running risk-reducing review passes that analyze workspace changes. These passes inspect changed files and apply targeted quality checks, prioritizing blocking issues and classifying their severity for structured output.