pre-review

Analyze code diffs against develop with four parallel reviewer perspectives.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill pre-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-review
Source: https://github.com/Ledger-Wallet-LLC/ledgerwallet/tree/main/.cursor/skills/pre-review
Command: npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill pre-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-review standardizes and accelerates early-stage code reviews by analyzing diffs against develop, surfacing architecture, correctness, and quality issues before merge.

Core Features & Use Cases

  • Parallel evaluation by four focused agents (A: Architecture & MVVM compliance, B: Correctness & security, C: Code quality & conventions, D: General review) to ensure comprehensive coverage.
  • Consolidated findings grouped by severity with file:line references for quick remediation.
  • Guidance for merges and targeted fixes to reduce regressions and improve maintainability.

Quick Start

Run the pre-review on your current branch to generate a grouped, severity-sorted set of findings.

Frequently Asked Questions about pre-review

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

FAQPage Schema
How do I run a structured code review on a diff before merge?

Run a structured pre-review on your current branch to analyze diffs against develop, surfacing architecture, correctness, and quality issues before merge using four parallel agent perspectives.

What is the best way to automate pull request reviews for architecture and security?

Automate pull request reviews by applying four parallel agents to evaluate architecture, correctness, security, and code conventions, generating a standardized output grouped by severity with file:line references.

Can I analyze code quality and conventions using parallel review agents?

Yes, you can analyze code quality and conventions using agent C, which runs in parallel with architecture, correctness, and general review agents to ensure comprehensive coverage of code changes.

Does pre-review require a diff against the develop branch to work?

Pre-review requires a diff against the develop branch to function, as it analyzes these code changes to provide consolidated findings grouped by severity and guidance for targeted fixes.

How are code review findings grouped for quick remediation?

Code review findings are consolidated and grouped by severity with file:line references, providing guidance for merges and targeted fixes to reduce regressions and improve maintainability.

When do I need to use a pre-review process for my commits?

Use a pre-review process when you need to standardize and accelerate early-stage code reviews, ensuring commits affecting architecture, correctness, and quality are evaluated before merging into develop.