pr-spec-review

Reviews pull requests against ICEA and Tech Spec requirements with traceability matrices and merge verdicts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Verifying that a pull request actually implements what the approved spec requires is slow and error-prone when done manually. This Skill automates spec-to-code compliance checking, producing a structured review that shows exactly which requirements are implemented, partial, missing, or unverifiable. ## Core Features & Use Cases - Four-Part Compliance Report: Generates a Spec Compliance Check, Code Review Against Spec, Traceability Matrix, and Gaps/Risks Report with file-and-line evidence for every finding. - Dual Scope and Output Modes: Supports ICEA-only reviews before a Tech Spec exists, full ICEA+Tech Spec reviews with coverage-matrix and D-option fidelity checks, and a compact verdict block used by pr-create and checkin gates. - Provider-Aware PR Fetching: Resolves PR diffs from GitHub or Azure DevOps by PR number, from saved diff files, or from the local branch against the base branch. - Use Case: A developer finishes a feature branch for ADO work item 1234 and runs the review; the Skill auto-discovers the ICEA and Tech Spec from the story folder, diffs against the base branch, and returns a merge verdict listing any missing acceptance criteria. ## Quick Start Ask the assistant to review the current branch's pull request against the approved ICEA and Tech Spec for the work item and report any missing requirements.

Frequently Asked Questions about pr-spec-review

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

FAQPage Schema
How do I review a pull request against a spec document?

Provide the spec file path and optionally a PR number or diff file, and the Skill compares every requirement in the spec against the code changes. It returns a compliance check, traceability matrix, and merge verdict with file-and-line evidence.

How do I check if a PR implements all acceptance criteria?

The Skill parses each acceptance criterion from the ICEA document and maps it to the PR diff, marking each as implemented, partial, missing, or unclear. Missing criteria block the merge verdict with a FAIL status.

Can I review a GitHub or Azure DevOps PR by number?

Yes, passing a PR number triggers provider-aware fetching that resolves the base and head refs via the GitHub or Azure DevOps API and computes the diff locally. The gh or az CLI is optional; curl and git work as a fallback.

What is the difference between ICEA-only and full scope review?

ICEA-only scope checks acceptance criteria compliance, used before a Tech Spec is approved. Full scope additionally verifies the Tech Spec's AC coverage matrix against the diff and checks D-option fidelity for undocumented design drift.

What happens if a requirement cannot be verified from the diff?

Requirements describing runtime behavior that cannot be confirmed from code changes are marked as unclear rather than silently skipped. The finding explains why verification was impossible and requests developer confirmation.