worktree-ux-pr

Git worktree rebasing for UX pull requests is automated by rebasing worktrees on origin/dev and force-pushing when history changes. This coordinates scripted rebases to reduce manual synchronization and error-prone handoffs across enterprise repos.

Yes, capturing UI verification evidence and attaching it to a PR automatically is supported. The workflow coordinates headless Chrome MCP verification, uploads screenshots as assets, and comments on PRs with references to the captured evidence for traceability.

A worktree-based UX PR workflow is a process of rebasing isolated development branches, verifying UI changes, and attaching evidence to pull requests. You need it for enterprise repos with multiple UX PR worktrees requiring synchronized rebases and UI verification.

Yes, Chrome MCP is used to guide headless UI verification within the worktree workflow. It coordinates with the UI server to capture screenshots and verify interface changes before uploading assets and commenting on the PR.

The best way to synchronize multiple UX PR worktrees against origin/dev is running an automated rebase-worktrees script. It reads environment overrides to tailor worktree paths, enforces rebasing on origin/dev, and force-pushes when history changes.

If your worktree rebase fails to attach evidence to the pull request, the UI server may not have started correctly for headless Chrome MCP verification. Ensure environment overrides are configured properly to tailor worktree paths and server behavior.