wtf.pr-review

Compare pull request diffs against linked Task specs to identify spec drift.

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtf.pr-review
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.pr-review
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers and tech leads review pull requests by comparing diffs to the linked Task specification (Gherkin scenarios, Contracts, and Impacted Areas) to identify spec drift, missing tests, and contract violations before merge.

Core Features & Use Cases

  • Read and evaluate diffs against the Task spec to verify alignment with Gherkin scenarios and contract constraints.
  • Retrieve and reference the Task hierarchy from linked issues to guide the review and ensure coverage across Epics, Features, and Tasks.
  • Generate a structured GitHub PR review that highlights findings, suggestions, and any gaps relative to the spec, returning to the developer for resolution.

Quick Start

Prompt the AI to review a specific PR against its linked Task spec and generate a structured PR review.

Frequently Asked Questions about wtf.pr-review

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

FAQPage Schema
How do I review a pull request for spec drift and missing tests?

To review a pull request for spec drift, compare the PR diff against the linked Task spec, including Gherkin scenarios and Contracts, to identify misalignments and missing tests before merging.

What is spec adherence in a GitHub PR review?

Spec adherence in a PR review verifies that code changes align with the Task hierarchy and acceptance criteria, ensuring Gherkin scenarios and contract constraints are met without drift.

Can I check Gherkin scenario coverage automatically from a PR diff?

Yes, you can check Gherkin scenario coverage by parsing the PR diff and evaluating it against the linked Task spec to verify alignment and flag missing tests or contract violations.

How do I generate a structured PR review from impacted areas and contracts?

Generate a structured PR review by loading the steering doc, retrieving the Task hierarchy, analyzing impacted areas, and producing findings that highlight spec gaps and contract violations for the developer.

Does this PR review approach work without external dependencies?

Yes, the PR review approach works without external dependencies, relying solely on the linked Task spec, Gherkin scenarios, and Contracts to evaluate diff alignment and generate structured findings.

When should I use contract validation during code review?

Use contract validation during code review when a pull request modifies impacted areas that must align with defined Contracts and Gherkin scenarios, ensuring no spec drift occurs before merge.