review

Analyze uncommitted diffs, recent commits, or current branch for quality and correctness issues.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill review-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/review
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill review-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In-progress changes often drift away from established project standards, leading to late discoveries of issues during reviews. This skill provides a structured workflow to inspect diffs, commits, and runbook-aligned changes to ensure quality, consistency, and adherence to guidelines before merging.

Core Features & Use Cases

  • Structured review of uncommitted changes, recent commits, and the current branch to surface quality issues.
  • Alignment with project standards and runbooks, including checks for code quality, design conformity, testing, and security.
  • Use Case: A developer wants a pre-PR quality gate that surfaces potential defects and guideline violations before submission.

Quick Start

Review a specific scope (uncommitted changes, recent commits, or current branch) and request a formal review report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review uncommitted changes for code quality and compliance?

To review uncommitted changes for code quality and compliance, analyze the diffs against project standards. This process surfaces potential defects, guideline violations, and design conformity issues, producing a structured report before merging.

What is a pre-PR quality gate for recent git commits?

A pre-PR quality gate for recent git commits is a structured workflow that inspects branch changes to ensure quality, consistency, and adherence to runbook guidelines before submission. It identifies correctness issues across code, testing, and security.

Can I check my current git branch for design conformity and security issues?

Yes, you can check your current git branch for design conformity and security issues by analyzing the changes against established guidelines. This generates a formal review report covering code quality, testing, and compliance.

How do I ensure in-progress changes adhere to project runbook guidelines?

To ensure in-progress changes adhere to project runbook guidelines, inspect uncommitted diffs and recent commits for alignment with established standards. This surfaces deviations in testing, security, and code quality before merging.

What is the best way to surface defects in uncommitted git diffs before submission?

The best way to surface defects in uncommitted git diffs is to run a structured quality review that checks for correctness, design conformity, and compliance. This produces a report identifying potential problems before a PR is created.