icea-review

Reviews pull requests and diffs against approved ICEA acceptance criteria for compliance.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill icea-review-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: icea-review
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/icea-review
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill icea-review-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers need a fast way to verify that a pull request or code diff actually satisfies the approved ICEA acceptance criteria before requesting human review, without manually cross-checking every criterion against the changes. ## Core Features & Use Cases - ICEA Compliance Review: Validates a PR or diff against the approved ICEA acceptance criteria and produces a structured pass/fail compliance report with a merge verdict. - Automatic Spec Discovery: Auto-discovers the ICEA document for the branch's Azure DevOps work item ID and builds a diff-to-acceptance-criteria traceability map. - Compact Verdict Mode: Supports a compact verdict block output consumed by the checkin gate, plus pass-through of spec, pr, and diff arguments. - Use Case: Before opening a PR for human review, ask for a self-review of your diff against the spec to catch missing acceptance criteria and business-context severity issues early. ## Quick Start Ask the assistant to review my current diff against the approved ICEA spec and tell me whether it passes compliance.

Frequently Asked Questions about icea-review

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

FAQPage Schema
How do I review a pull request against an ICEA specification?

Invoke the review with your PR or diff and it validates the changes against the approved ICEA acceptance criteria, producing a four-part compliance report with a merge verdict. The ICEA document is auto-discovered from the branch's Azure DevOps work item ID.

What is the difference between icea-review and pr-spec-review?

icea-review is a thin alias for pr-spec-review with the --icea-only scope, checking only ICEA acceptance criteria. pr-spec-review additionally checks Tech Spec design compliance, so icea-review is useful before a Tech Spec is approved.

Can I check my diff against the spec before a Tech Spec is approved?

Yes, the --icea-only scope skips Tech Spec design checks entirely and validates only against ICEA acceptance criteria. This makes it suitable for early self-review before full specification approval.

Does the compliance report support a compact output format?

Yes, passing --compact emits a compact verdict block instead of the full four-part report. This compact form is what the checkin command's Check B consumes during its gate evaluation.

Can business-context severity findings be waived in the review?

No, business-context (B-series) severity escalation is applied by the review engine per the shared severity spec and is explicitly non-waivable. Findings flagged at that severity must be addressed before a passing verdict.