verifylisted

Verifies a feature branch in an isolated sandbox — extracts the test plan from the PR, generates verification items from the branch diff, creates a git worktree sandbox, runs automated checks, launches parallel agents for functional verification, and reports results. Never pushes to remote. Use before merging a feature branch to prove it works as described in the PR.
oprogramadorreal/optimus-claude · ★ 57 · Code & Development · score 82

Install: claude install-skill oprogramadorreal/optimus-claude

# Verify Feature Branch Prove that a feature branch works as described. Extract or generate a verification plan, create an isolated sandbox (git worktree), run automated checks and functional verifications, report results. All work happens inside the sandbox — the main workspace and remote repository are never modified. This skill complements `/optimus:code-review` (static analysis) by adding dynamic execution — it actually runs the code to confirm behavioral claims. ## Step 1: Pre-flight Read `$CLAUDE_PLUGIN_ROOT/skills/init/references/multi-repo-detection.md` for workspace detection. If a multi-repo workspace is detected, process each repo independently: run Steps 1–9 inside the repo the user is targeting. If ambiguous, ask which repo. All git commands in subsequent steps must run inside the selected repo directory (e.g., `git -C <repo-path> ...` or `cd <repo-path>`) — the workspace root has no `.git/` and git commands would fail there. ### Verify branch state 1. Confirm the current directory is inside a git repository 2. Detect the default branch using the algorithm in `$CLAUDE_PLUGIN_ROOT/skills/pr/references/default-branch-detection.md`. If no default branch can be determined → inform the user: "Could not detect the default branch. Ensure `origin` is configured and has been fetched." Stop. 3. Get the current branch: `git rev-parse --abbrev-ref HEAD` 4. **If on the default branch** — stop and explain: ``` ## Not on a feature branch /optimus:verify validates featur