review

Execute quality gates on git changes to verify test coverage and architecture.

1|Updated May 13, 2026

Search Tags:#git #workflow #testing #architecture #quality assurance #code review

Ready to run

npx skills add https://github.com/Amirault/DevGate --skill review-amirault

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Amirault/DevGate/tree/main/.agents/skills/review
Command: npx skills add https://github.com/Amirault/DevGate --skill review-amirault

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, grep, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of inconsistent code quality and incomplete verification before human review by enforcing a rigorous, impact-aware validation process.

Core Features & Use Cases

Impact-Aware Review: Automatically traces the blast radius of git changes to identify ripple-effect gaps in downstream consumers.
Automated Quality Gates: Enforces test coverage, architecture boundaries, and build status against specific acceptance criteria.
Use Case: Use this skill when you have finished implementing a feature and need to ensure your changes are safe, tested, and architecturally sound before requesting a human sign-off.

Quick Start

Run the review skill to validate that your current git changes meet all acceptance criteria and architectural standards.

Frequently Asked Questions about review

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

FAQPage Schema

How do I validate code quality and test coverage before a git pull request?▼

Automated quality gates validate code quality by executing test coverage verification and architecture boundary checks against your current git changes. This process traces the blast radius of modifications to identify ripple-effect gaps in downstream consumers before requesting human review.

What is impact-aware analysis for software changes?▼

Impact-aware analysis traces the blast radius of git changes to identify ripple-effect gaps in downstream consumers. It ensures modifications do not introduce untested regressions across system boundaries by automatically verifying that all affected components meet specific acceptance criteria.

Does this automated code review require specific command-line dependencies?▼

Yes, this automated code review requires a bash environment with git, jq, and grep installed. These dependencies are necessary to parse changes, query data structures, and execute the quality assurance scripts that verify build status and test coverage against your repository.

How do I enforce architectural boundaries in a development workflow?▼

Automated quality gates enforce architectural boundaries by assessing build status and detecting ripple-effects across system boundaries. This validates that current git changes align with required architectural standards and spec requirements before implementation readiness is approved.

What are the limitations of automated quality gates for code review?▼

Automated quality gates are limited to verifying technical requirements like build status, test coverage, and impact-aware analysis across system boundaries. They serve to validate implementation readiness rather than replace human sign-off, ensuring changes are safe and tested before manual review.