review

Assess code changes across six lenses and generate a structured report.

36|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/cagdotin/agents --skill review-cagdotin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/cagdotin/agents/tree/main/skills/engineering/review
Command: npx skills add https://github.com/cagdotin/agents --skill review-cagdotin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Review Skill provides a reusable, governance-focused approach to evaluating code changes, diffs, or files for correctness, architectural alignment, security, quality, testing coverage, and dependency risk.

Core Features & Use Cases

  • Load and apply six lenses (architecture, correctness, security, quality, testing, dependencies) to a change set.
  • Determine scope, gather context, and produce a structured, lens-driven report that highlights meaningful insights.
  • Works across local diffs, staged changes, branch comparisons, or targeted files, and outputs a standardized assessment.

Quick Start

Provide the diff or target files to begin a structured, lens-driven review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code changes for security and architecture risks?

A structured code review assesses changes across six lenses: architecture, correctness, security, quality, testing, and dependencies. It works with local diffs, staged changes, or branch comparisons to yield a standardized governance report highlighting meaningful insights.

What is the best way to analyze a git diff for correctness and testing coverage?

The best way to analyze a git diff for correctness and testing coverage is to apply a multi-lens review process. This approach evaluates your branch comparisons or staged changes, specifically targeting testing coverage and correctness to generate a structured assessment report.

Can I perform a structured code review on specific files instead of a full branch diff?

Yes, you can perform a structured code review on specific files instead of a full branch diff. The review process is applicable to local diffs, staged changes, branch comparisons, or targeted individual files, adapting its lens-driven assessment to the provided scope.

Does this code review approach evaluate dependency risks alongside quality?

Yes, this code review approach evaluates dependency risks alongside quality. It loads six specific lenses—architecture, correctness, security, quality, testing, and dependencies—to ensure your code changes are assessed for external library risks and overall code governance.

How do I get a standardized report format from a staged changes code review?

To get a standardized report format from a staged changes code review, the assessment follows a predefined report format structure. It gathers context, applies the six review lenses, and outputs a structured, lens-driven report highlighting meaningful insights.