PAIR-code/deliberate-lab / .agents/skills/eval-pr
eval-pr
VerifiedSet up a git worktree to run and evaluate an upstream Pull Request locally in a flat worktree bare clone repository layout.
Evaluate Pull Request
This skill helps an AI assistant set up a clean, isolated git worktree to evaluate an upstream pull request (PR) locally. This ensures your active development workspace is completely unaffected while testing community contributions or colleague PRs.
When to use
Invoke this skill when the user asks to:
- "Set up a worktree to run PR locally"
- "Check out PR to test"
- "Evaluate pull request locally"
- "Set up a worktree for PR "
- "Update PR to the latest"
- "Refresh my local copy of PR "
- "Sync PR worktree"
- "Pull new changes for PR "
[!TIP] Pair with
pr-test-plan: Before or after checking out a PR worktree, invoke thepr-test-planskill to determine if runtime testing is required and synthesize a 7-part manual experiment verification plan.
Prerequisites
The local repo must have a triangle workflow configured with:
originpointing to the user's fork (e.g.jimbojw/deliberate-lab)upstreampointing to the canonical repo (PAIR-code/deliberate-lab)
Verify with git remote -v.
It also assumes a bare repository layout with flat worktrees (e.g. main/, feature branches, and .bare/ reside under a single parent directory). Verify this layout with:
git worktree list
Procedure
Step 1 — Fetch the PR branch
Intent: Fetch the pull request branch directly from upstream without adding the contributor's remote.
You can inspect the PR status and metadata first using the GitHub CLI:
gh pr view <PR-NUMBER> --json number,title,state,headRefName
[!NOTE] While
gh pr checkoutis common in standard single-checkout repos, in Deliberate Lab's bare repository layout, usegit fetchandgit worktree addas described below to maintain flat sibling worktrees.
Run the following command from the repo root:
git fetch upstream pull/<PR-NUMBER>/head:pr-<PR-NUMBER>
This fetches the head of PR <PR-NUMBER> and creates a local branch named pr-<PR-NUMBER>.
Step 2 — Determine worktree path and add worktree
Intent: Add a new worktree directory as a sibling to the existing worktree directories.
- Find the parent directory of your current worktree. For example, if your current worktree is at
/path/to/checkout/deliberate-lab/main, the parent is/path/to/checkout/deliberate-lab/. - Determine the path for the new worktree (e.g.,
../pr-<PR-NUMBER>). - Add the worktree:
git worktree add ../pr-<PR-NUMBER> pr-<PR-NUMBER>
Step 3 — Handover
Once the worktree is created, inform the user that it is ready and provide the path to switch to. The user will handle installing dependencies, building, and running the project from their IDE/terminal.
Step 4 — Formulate Manual Test Plan (pr-test-plan)
Before or after switching into the evaluation worktree, invoke the pr-test-plan skill to audit the author's test plan or synthesize Deliberate Lab's canonical 7-part experiment test plan:
- Verifies whether the PR alters user-experienced runtime behavior vs. non-runtime paths or pure refactors.
- Deduces template, stages sequence, cohort size, agent mediator/participant configs, tester actions, and success criteria.
- Provides a step-by-step walkthrough for manual verification in
./run_locally.sh.
Updating an Existing PR Worktree
If the PR author has pushed new commits and the user wants to refresh their local copy, follow this procedure instead of Steps 1–3.
Detect an existing worktree
Before running the initial setup steps, check whether a worktree for the PR already exists:
git worktree list
If a worktree named pr-<PR-NUMBER> already exists, skip Steps 1–3 and continue with the update procedure below.
Update procedure
From inside the existing PR worktree directory (e.g. ../pr-<PR-NUMBER>):
# 1. Fetch the latest PR head from upstream
git fetch upstream pull/<PR-NUMBER>/head
# 2. Reset the local branch to match
git reset --hard FETCH_HEAD
[!IMPORTANT] Why
git reset --hard FETCH_HEAD? This is someone else's PR — we should not rebase or merge. We want our local branch to be an exact mirror of whatever the PR author has pushed.reset --hardachieves this cleanly.
[!WARNING] If the user has made local modifications to the PR branch (e.g. experimental changes while testing),
git reset --hardwill discard them. Warn the user before running this command ifgit statusshows uncommitted changes or ifgit logshows local commits beyond the PR's original commits.
After the reset, the user will likely need to reinstall dependencies and rebuild (e.g. npm ci, npm run build -w utils, etc.).
Cleanup when done (Optional reference)
If the user asks to clean up the PR worktree later, or for their reference:
- Ensure the user is not actively inside the worktree directory in their terminal.
- Remove the evaluation worktree:
git worktree remove ../pr-<PR-NUMBER> - Delete the local evaluation branch:
git branch -d pr-<PR-NUMBER>
Safety & Style Rules
- Do NOT nest worktrees: Never run
git worktree addto create a directory inside an existing worktree directory. Always place it as a sibling under the main checkout directory. - Do NOT use
-Dto delete branches: Always usegit branch -d(lowercase) so git can confirm there are no unmerged commits before deletion. - Never rebase or merge someone else's PR branch: The goal is to mirror the PR exactly, not to modify its history or mix in other changes.
- Always warn about uncommitted changes: Before running
git reset --hard, checkgit statusandgit logfor local modifications or commits that would be lost.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |