pr-test

Plans and runs local validation of GitHub pull requests in isolated worktrees.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-test-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-test
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/qvac/.cursor/skills/pr-test
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-test-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Validating a pull request locally usually means checking out branches, figuring out which packages changed, and guessing which tests to run. This Skill automates that process for tetherto/qvac PRs by preparing an isolated worktree, discovering touched packages and their scripts, and recommending an appropriate test tier without ever touching your working tree. ## Core Features & Use Cases - Isolated PR worktree preparation: Fetches the PR into a cached worktree under ~/.cache/qvac-pr-review so your local repository state is never modified. - Automated test discovery: Detects touched packages, package.json scripts, changed examples, and related e2e filters, then recommends a validation tier from T1 (examples) through T7 (full mobile suite). - Tiered execution with safety boundaries: Runs agent-safe steps like installs, builds, and examples inside the worktree, while handing SDK e2e commands that need npm auth or devices to the user with exact shell-ready commands. - Use Case: A reviewer receives a PR URL touching the SDK transcription module. The skill prepares the worktree, proposes T2 with transcription examples and e2e filters, runs the safe steps, prints the manual e2e command block, and summarizes pass/fail results from the report directory. ## Quick Start Ask the assistant to test the pull request at https://github.com/tetherto/qvac/pull/1234 using the pr-test skill.

Frequently Asked Questions about pr-test

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

FAQPage Schema
How do I test a GitHub pull request locally without changing my working tree?

Provide the PR URL and the skill prepares an isolated worktree under ~/.cache/qvac-pr-review using worktree-prepare.mjs. All installs, builds, and tests run inside that worktree, so commands like git checkout or git stash are never run against your main repository.

How do I choose which tests to run for a pull request?

The discovery helper inspects the committed PR state and recommends a tier from T1 (changed examples) through T7 (full mobile suite). SDK changes default to T2 covering install, build, changed examples, and changed e2e on desktop, and you can override the recommendation.

Can the agent run SDK e2e tests automatically?

No. SDK tests-qvac setup and qvac-test run:local commands require npm/GitHub Packages auth and device access, so they are printed as exact POSIX or PowerShell command blocks for the user to run manually. The agent only runs package installs, builds, and changed examples.

Does PR validation support mobile testing on Android or iOS?

Yes. Tiers T3, T5, and T7 include mobile validation, and the skill asks which platform (android or ios) to target. Non-SDK packages use mobile scripts only if their package.json exposes them.

What happens if the PR worktree preparation fails?

The skill enters fallback mode: it fetches files via the GitHub API and obtains the patch with gh pr diff. Local command execution is unavailable in fallback mode unless the user retries worktree preparation.