pr-local-preview-maintainer

Run GitHub pull requests in isolated local worktrees with preview URLs.

280|30|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Undertone0809/rudder --skill pr-local-preview-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-local-preview-maintainer
Source: https://github.com/Undertone0809/rudder/tree/main/.agents/skills/maintainer/pr-local-preview-maintainer
Command: npx skills add https://github.com/Undertone0809/rudder --skill pr-local-preview-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of reviewing a GitHub pull request locally without risking your current working tree or losing a clear, inspectable preview URL.

Core Features & Use Cases

  • Isolated local worktree preview: creates or reuses a sibling worktree so local changes are protected while the PR is checked out for review.
  • Safe, isolated runtime configuration: starts Rudder using dedicated RUDDER_INSTANCE_ID and free ports to avoid stepping on other local sessions.
  • Readiness verification and actionable hand-off: verifies startup health and returns a stable local URL plus log/stop commands, with optional UI screenshot capture for visual changes.
  • When UI changes matter: captures browser-relevant screenshots outside the repo when the PR touches UI/visual areas or when the user requests “see the effect”.

Quick Start

Tell the assistant: “Check out PR 8 locally, run the preview on an isolated port, verify it’s healthy, and give me the local URL (and screenshots if needed).”

Frequently Asked Questions about pr-local-preview-maintainer

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

FAQPage Schema
How do I preview a GitHub PR locally without affecting my current worktree?

Run a GitHub PR in an isolated local worktree to preview it safely without affecting your current working tree. This method checks out the pull request in a separate sibling directory, protecting your main workspace while providing a verifiable local preview URL for review.

How can I run multiple local dev servers on different ports for PR review?

Run multiple local dev servers for PR review by selecting free ports and assigning a dedicated instance ID for each session. This isolated runtime configuration prevents port conflicts and ensures that parallel local preview sessions do not step on each other.

Can I capture UI screenshots when previewing a GitHub pull request locally?

Yes, you can capture UI screenshots when previewing a GitHub pull request locally. If the PR touches visual areas or you request to see the effect, the preview process can capture browser-relevant screenshots outside the repository for verification.

Does starting a dev server in a persistent tmux session help with local PR preview?

Starting a dev server in a persistent tmux session ensures the local PR preview remains running in the background safely. This allows you to continue working in your terminal while the server starts, polls for readiness, and provides a stable local URL for review.

What is the best way to verify a local dev server is ready before opening a PR preview?

The best way to verify a local dev server is ready before opening a PR preview is through readiness polling. This process checks the startup health of the dedicated instance and returns actionable open, log, and stop instructions only after confirming the local URL is stable.

What limitations exist when checking out a GitHub PR in a local worktree?

A key limitation when checking out a GitHub PR in a local worktree is the need to manage dedicated instance IDs and free ports carefully. Without proper isolated runtime configuration, parallel local sessions may conflict, impacting the safe verifiable preview URL.