By name: pr-test description: Test a GitHub PR locally to verify it solves the customer issue and has no regressions. Use when the user asks to "test a PR", "test PR #123", "test this pull request", or wants to manually verify PR changes before merging.
Test PR Locally
This skill guides manual testing of a GitHub pull request to verify it solves the customer problem and doesn't introduce regressions. CI handles automated tests - this is about behavioral verification.
Workflow
1. Fetch PR and Ticket Context
gh pr view <PR_NUMBER> --json title,body,headRefName,baseRefName,files,additions,deletions
Understand:
- The customer problem - what pain point does this solve?
- Acceptance criteria - what does "done" look like?
- Changed files - what areas might have regressions?
2. Checkout and Setup
gh pr checkout <PR_NUMBER>
Start the local dev environment. If something fails to start, STOP and verify with the user - is this a known local env issue or something the PR broke?
3. Verify Local Environment Works
Before testing PR changes, confirm the baseline works:
- Can you reach the relevant page/endpoint?
- Does the existing functionality in that area work?
If baseline doesn't work: Stop and troubleshoot. This is likely a local env issue, not a PR regression. Common causes:
- Missing env vars
- Database not migrated
- Services not running
- Wrong branch dependencies
4. Test the Customer Problem is Solved
Walk through each test step with the user - don't run autonomously. For each test:
- Explain what you're about to verify
- Execute the test
- Share results and confirm before moving on
5. Check for Regressions
Test adjacent functionality that might be affected:
- Other features on the same page/endpoint
- Related workflows that share code paths
- API consumers if changing backend
If something doesn't work:
- STOP - don't continue testing
- Check if the issue exists on the base branch
- If base branch also broken → local env issue, not regression
- If base branch works → actual regression, report it
6. Post Results to PR (After Validation)
After user validates findings, post a comment:
gh pr comment <PR_NUMBER> --body '<COMMENT>'
Format:
## Manual Testing Results
**Ticket:** LT-XXXX - [ticket title]
### Customer Problem Solved?
✅ Yes / ❌ No - [brief explanation]
### Regression Check
| Area | Result |
|------|--------|
| [related feature] | ✅ or ❌ |
<details>
<summary>Test details</summary>
[Commands run, observations, screenshots if relevant]
</details>
Key Principles
- CI handles automated tests - don't run test suites, focus on behavior
- Understand the customer problem first - test against the ticket, not just the code
- Stop on failure - distinguish local env issues from real regressions before continuing
- Collaborative - walk through with user, don't run autonomously
- Only post after user validates - summarize and confirm before commenting on PR