verify-pr

Orchestrates manual verification of open PRs against a hermetic per-PR stack.

1|1|Updated Oct 3, 2021
One-click install
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill verify-pr-benjr70
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-pr
Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/verify-pr
Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill verify-pr-benjr70

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests often carry manual-verification checklists that nobody runs, leaving UI regressions and broken flows to slip into merges. This Skill automates one full verification round per PR: it parses the checklist, boots an isolated per-PR stack, drives a real browser and Electron shell through a verifier agent, and reconciles honest results back onto the PR. ## Core Features & Use Cases - Checklist-driven verification: Parses unchecked items from the PR body, spawns a manual-verifier agent to exercise each item in headful Chrome or the Electron shell, and ticks only the boxes that genuinely passed. - Hermetic per-PR stack: Boots the PR's own code in an isolated Docker compose project with a synthetic temperature feed, then tears everything down unconditionally on any exit path. - Screenshot tours for UI changes: Detects UI-affecting diffs, captures viewport-correct screenshots (Pixel 10 Pro for frontend, 800x480 kiosk panel for smoker), and posts them into the PR description. - Use Case: A reviewer types "/verify-pr 412" and receives ticked checklist boxes, one consolidated evidence comment with logs and screenshots, and a machine-readable manual-verify summary line — without manually testing anything. ## Quick Start Run "/verify-pr <PR number>" against any open pull request that contains a manual verification checklist.

Frequently Asked Questions about verify-pr

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

FAQPage Schema
How do I run manual verification on a GitHub pull request automatically?

Invoke /verify-pr with the PR number. The skill parses unchecked checklist items, boots a hermetic per-PR stack, spawns a verifier agent to test each item in a real browser or Electron shell, then ticks passing boxes and posts one evidence comment.

What happens when the verification stack fails to boot?

A boot failure after the built-in retry is treated as an infrastructure error, not a verdict. The skill posts a distinct infra-error comment, emits a manual-verify: infra-error line with zero item verdicts, and never fabricates PASS or FAIL results.

Does verify-pr capture screenshots for UI changes?

Yes. A file-path detector identifies UI-changing diffs, and the verifier captures viewport-clipped screenshots per surface: 427x952 for the mobile frontend and 800x480 for the smoker kiosk panel. The --force-tour flag forces capture regardless of the detector.

Can verify-pr test the Electron desktop app without a display?

It requires the box's live GNOME/XWayland session, resolved through a shared display library. An unset shell DISPLAY is not evidence of headlessness; only the resolver returning non-zero is a legitimate no-display signal, reported as an infrastructure finding.

What are the limitations of verify-pr verification rounds?

Deployed-environment and hardware items are deferred with a demanded spec or named blocker rather than tested. The wifi indicator is verified only through store state, and shell-affecting PRs defer shell-specific behavior because the Electron main process runs from the provisioned checkout.