convergence-review

Review git diffs against the base branch for correctness and quality.

2|Updated Mar 31, 2026

Search Tags:#testing #architecture #security #quality #diff #code-review #base-branch

Ready to run

npx skills add https://github.com/c-sonnier/convergence --skill convergence-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convergence-review
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/review
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review the actual code diff against the base branch to ensure the implementation aligns with design and quality expectations.

Core Features & Use Cases

Stage 0 — Get the Diff: Load the git diff against the base branch for reference.
Stage 1 — Correctness: Verify that code changes implement the designed decisions and that all outline stages are complete, identifying any missing or extra requirements.
Stage 2 — Quality: Assess architecture, security, data safety, code quality, tests, and pattern consistency; compile actionable findings to guide merges.
Use Case: After implementing a feature or evaluating a PR, perform this review to determine readiness for merging.

Quick Start

Run git diff <base-branch>...HEAD and begin the two-stage review following the outlined steps.

Frequently Asked Questions about convergence-review

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

FAQPage Schema

How do I review a git diff against the base branch before merging?▼

You can review a git diff against the base branch by loading the diff output and running a two-stage evaluation that first verifies correctness against the design outline, then assesses architecture, security, data safety, tests, and pattern consistency.

What does a two-stage code review check for in a pull request?▼

A two-stage code review first verifies that code changes accurately implement designed decisions and complete all outline stages, then evaluates code quality across architecture, security, data safety, tests, and pattern consistency to guide merges.

How do I verify code correctness against a design outline after implementation?▼

You verify code correctness against a design outline by comparing the actual git diff against the base branch to confirm all designed decisions are implemented, outline stages are complete, and any missing or extra requirements are identified.

Can I assess architecture and security quality directly from a git diff?▼

You can assess architecture and security quality from a git diff by evaluating the changes against the base branch to compile actionable findings regarding data safety, code quality, tests, and pattern consistency for merge evaluation.

When do I need to perform a rigorous code review of my diffs?▼

You need to perform a rigorous code review of your diffs after implementing a feature or evaluating a PR to ensure implementation accuracy and code quality before merging into the base branch.

What inputs are required to evaluate code quality and correctness before a merge?▼

Evaluating code quality and correctness before a merge requires access to the git diff against the base branch, the design outline, and relevant tests to accurately assess implementation and quality across multiple dimensions.