review

Review code against architectural, security, and design specifications.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill review-ambrovia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/review
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill review-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of biased or superficial code reviews by enforcing a structured, multi-lens audit that separates the builder from the reviewer, ensuring contract adherence and architectural integrity.

Core Features & Use Cases

  • Six-Lens Audit: Systematically evaluates code through architecture, design, security, adversarial, simplification, and AI-slop lenses.
  • Acceptance Criteria Verification: Maps every requirement from the work package to concrete evidence of completion.
  • Use Case: Use this during the final phase of a development pipeline to ensure that a complex feature implementation meets all security standards and architectural invariants before it is marked as done.

Quick Start

Invoke the review skill to perform a comprehensive audit of the current work package against its approved technical plan and acceptance criteria.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a comprehensive code review for high-integrity software delivery?

A comprehensive code review evaluates implementations against architectural, security, and design specifications to ensure strict adherence to acceptance criteria and prevent regressions in software pipelines.

What is a multi-lens code audit and when do I need it?

A multi-lens code audit systematically evaluates code through architecture, design, security, adversarial, simplification, and AI-slop lenses to enforce contract adherence and architectural integrity in software development pipelines.

How do I verify acceptance criteria compliance before merging code changes?

Verifying acceptance criteria compliance requires mapping every requirement from the work package to concrete evidence of completion, ensuring objective, persona-driven verification of code changes to maintain system quality.

Does this code review skill work with existing software development pipelines?

This code review skill applies to software development pipelines requiring strict adherence to project-specific coding standards, performing a read-only audit during the final phase of feature implementation.

What's the best way to prevent regressions and maintain architectural integrity during code review?

The best way to prevent regressions is enforcing a structured, multi-lens audit that separates the builder from the reviewer, ensuring objective verification of code changes against approved technical plans.

Can I run a security audit and architecture verification on the same code review pass?

Yes, a security audit and architecture verification can run simultaneously by systematically evaluating code through architecture, design, security, adversarial, simplification, and AI-slop lenses in one comprehensive read-only review.