skills.rest
JYeswak
JYeswakCOMMUNITY
Explore all skills by this author →
Website𝕏@ZestStreamGitHub

pr-verify

Verifies patches by running the reproduction before and after the change.

Updated Sep 11, 2026
Search Tags:#git#code review#pull request#bug fix#reproduction#regression test#patch verification
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill pr-verify-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-verify
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/pr-verify
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill pr-verify-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claimed fixes are often asserted without evidence: the regression test never failed before the patch, the repro was only run on the patched tree, or the failure was environmental. This Skill proves whether a patch actually fixes its claimed reproduction by running the same repro twice on the same environment. ## Core Features & Use Cases - Before/After Verification: Runs the identical repro on the base commit and on the patched tree, quoting commands, outputs, and exit codes verbatim. - Regression Test Judgment: Runs any test added by the patch on the base commit to confirm it actually fails there and covers the bug. - Neighbour Test Checks: Runs the tests owned by the changed files so the fix is not trading one failure for another. - Use Case: A reviewer is asked to confirm a PR fixes a reported crash. The Skill checks out the base commit, reproduces the crash, applies the patch, reruns the repro, and issues a dated verdict of verified, not verified, or blocked. ## Quick Start Ask the agent to verify whether the attached patch fixes the reproduction steps from the bug report and to report the before and after results.

Frequently Asked Questions about pr-verify

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

FAQPage Schema
How do I verify that a PR actually fixes a bug?▼

Run the exact reproduction on the base commit to confirm it fails, apply the patch, then run the identical repro again to confirm it passes. One run proves nothing; a fix is verified only by fails-before and passes-after on the same environment.

How to check if a regression test actually covers the bug?▼

Run the added test on the base commit without the patch. It must fail there; if it passes on the pre-patch tree, it is not a regression test for this bug and should be reported as non-covering.

What happens if the reproduction cannot be run?▼

The verdict is blocked, never looks-correct. Reading a diff is review, not verification, so the report states what could not run and what would unblock it instead of issuing a verdict from inspection.

Can this skill merge or modify the patch during verification?▼

No. It never merges, pushes, tags, deploys, or amends the patch, since a modified patch is a different patch. Merging requires the owner's explicit approval and happens outside the verification workflow.

Why run neighbour tests instead of the full test suite?▼

Neighbour tests are the tests owned by the changed files, so they catch the fix trading one failure for another without the cost of a full suite. Each neighbour result is listed individually rather than summarized as passing.

Related Skills

Explore More Software Engineering Skills→
pixel-cellarpixel-cellar
277

bug-report

Generate structured Markdown bug reports with reproduction steps and severity assessment.

Official
Intermediate
lhpaullhpaul
9

post-merge-cleanup

Automate local post-merge cleanup and issue tracker updates.

Community
Advanced
KYRIE66nbKYRIE66nb

review-code

Identify and report code-quality issues across PRs, diffs, and patches.

Community
Advanced
AgentSystemLabsAgentSystemLabs
121

check-pr-readiness

Run diff-scoped typechecking, linting, formatting, and tests on pull requests.

Official
Advanced