wa:validate-review

Aggregate validation gate outputs into a single verdict with rigor-based blocking rules.

Updated Mar 26, 2026

Search Tags:#code review #validation #security scanning #CI readiness #gate aggregation #UAT verdict #PR mergeability

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:validate-review
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/validate-review
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered quality, code, security, CI, and UAT outputs into a single, reliable pass/conditional/pass-or-fail decision with clear blocking and advisory items.

Core Features & Use Cases

Gate aggregation: Collates results from validation artifacts (quality, code review, security, CI, and UAT) and reports them in a unified table.
Rigor-based blocking rules: Applies lite/standard/strict severity mapping so advisory issues don’t block at lower rigor, while blocking issues always do.
Merge readiness checks: Uses PR state (approval, CI status checks, and mergeability) to incorporate merge-readiness into the final verdict.

Quick Start

Run the skill for the current feature context by entering: /validate-review.

Frequently Asked Questions about wa:validate-review

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

FAQPage Schema

How do I unify multiple code review and security scanning outputs into a single pass/fail decision?▼

Gate aggregation combines validation artifacts from quality, code review, security, CI, and UAT phases into a unified table. It evaluates pass criteria across these categories to produce a single deterministic pass, conditional, or fail verdict for your feature.

What is the best way to check PR mergeability alongside CI readiness and UAT results?▼

Merge readiness checks look up PR state, approval status, and CI status checks to incorporate mergeability directly into the final verdict. This ensures CI readiness and UAT results are evaluated together before deployment.

How does rigor-level classification affect security scanning and code review blocking rules?▼

Rigor-level classification applies lite, standard, or strict severity mapping to validation artifacts. Advisory issues do not block at lower rigor levels, while blocking issues always block, ensuring security scanning and code review severity scales appropriately.

Can I use gate aggregation for E2E lifecycle workflows that require consistent deployment decisioning?▼

Gate aggregation is designed for E2E lifecycle workflows where sub-skills produce gate reports requiring consistent decisioning before deployment. It scans mandatory artifacts and writes deterministic reports to ensure reliable deployment actions.

Do I need mandatory validation artifacts present to generate a UAT verdict?▼

Mandatory artifact presence checks are required before generating a UAT verdict. The validation process scans for these artifacts and evaluates pass criteria across quality, code review, security, CI, and UAT categories before writing the final report.

Why does my validation gate verdict show conditional instead of pass when advisory issues are present?▼

A conditional verdict occurs when advisory issues are present and the rigor-level classification is set to standard or strict. At lite rigor, advisory issues do not block the verdict, but higher rigor levels require them to be resolved before a full pass.