skills.rest
vinodkrishna221
vinodkrishna221COMMUNITY
Explore all skills by this author →
GitHub

pr-review

Reviews pull requests against task cards, contracts, and demo safety to produce a merge verdict.

Updated Aug 23, 2026
Search Tags:#git#code review#pull request#review checklist#merge verdict#contract fidelity#demo safety
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill pr-review-vinodkrishna221
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/pr-review
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill pr-review-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging pull requests without a structured review risks breaking the demo, violating API contracts, or letting scope creep slip into main. This Skill enforces a consistent six-gate review procedure so every PR is checked against its task card, contracts, and proof before merging. ## Core Features & Use Cases - Six-Gate Review: Checks card match, contract fidelity, proof of correctness, abstraction discipline, demo-path safety, and hygiene in a fixed order, stopping at the first failure. - Standardized Verdicts: Outputs a strict MERGE, FIX-THEN-MERGE, or BLOCK verdict with actionable file-and-line fixes and a normal/crunch bar setting. - Use Case: A reviewer opens a fresh session on a feature branch, reads the task card and touched contracts, runs the PR's check, and issues a verdict within 15 minutes — blocking a contract-breaking change before it reaches the demo. ## Quick Start Review the current pull request against its task card and contracts, then give me a MERGE, FIX-THEN-MERGE, or BLOCK verdict.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I review a pull request against a task card?▼

Fetch and check out the branch, read the task card in plans/ first, then the PR body and touched contracts, and only then the diff. Card-first reading prevents polished code from hiding the wrong deliverable.

What should a PR review checklist include before merging?▼

This review uses six gates: card match, contract fidelity against contract files, a runnable proof check, an abstraction audit, demo-path safety with seeded click-through, and hygiene for secrets, debug prints, and dead code.

When should a pull request be blocked instead of merged?▼

Block when there is a contract break, a red demo path, a committed secret, or no deliverable matching the task card. More than five fix items also means BLOCK with a recommendation to split the PR.

Can I merge my own pull request when working solo?▼

Solo mode requires running this review in a fresh agent session or a different tool than the one that built the PR. Self-merging without this independent review pass is not allowed.

What happens if a PR has no test or proof check?▼

Non-trivial logic without a check results in a FIX-THEN-MERGE verdict. The author must add the smallest assertion that would fail if the logic were broken, within a 20-minute fix timebox.

Related Skills

Explore More Software Engineering Skills→
EveryIncEveryInc
24.7k

ce-commit

Create git commits with clear, outcome-focused messages from staged or unstaged changes.

Official
Intermediate
missingbulbmissingbulb

merge-to-main

Merges the current branch or pull request into main using squash merge via GitHub.

Community
Intermediate
rust-worksrust-works
51

testing

Identify and address common testing anti-patterns across software projects.

Official
Intermediate
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced