isolated-birdhouse-web-testing

Orchestrates isolated Birdhouse web testing with port claiming, child browser agents, and artifact capture.

36|5|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Birdhouse-Labs/birdhouse --skill isolated-birdhouse-web-testing-birdhouse-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: isolated-birdhouse-web-testing
Source: https://github.com/Birdhouse-Labs/birdhouse/tree/main/.agents/skills/internal/birdhouse-development/isolated-birdhouse-web-testing
Command: npx skills add https://github.com/Birdhouse-Labs/birdhouse --skill isolated-birdhouse-web-testing-birdhouse-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Running browser-based tests against a Birdhouse feature branch risks port collisions, interference with other worktrees, and lost test artifacts. This Skill provides a structured workflow for spinning up disposable, isolated Birdhouse instances from a worktree and delegating browser validation to child agents. ## Core Features & Use Cases - Isolated Port Management: Claims a dedicated 20-port block per run using git-common-dir locks so parallel worktrees never collide. - Disposable Run Environments: Starts a detached Birdhouse server with a timestamped run directory containing workspace, screenshots, logs, and a database. - Child Agent Delegation: Teaches parent agents to hand off browser testing to reusable child agents that capture screenshots and MP4 recordings and report classified findings. - Use Case: You are verifying a feature branch against a new OpenCode version. Use this Skill to claim ports, launch an isolated instance from your worktree, delegate the browser validation to a child agent, and keep the full run directory for review until cleanup is approved. ## Quick Start Ask the agent to set up isolated Birdhouse web testing for the current worktree and delegate browser validation of a specific user flow to a child agent.

Frequently Asked Questions about isolated-birdhouse-web-testing

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

FAQPage Schema
How do I run isolated browser tests on a git worktree?▼

Claim a 20-port block with claim-isolated-port-range.sh, then start a detached Birdhouse server from the worktree using start-isolated-birdhouse.sh. Delegate the actual browser validation to a child agent that captures screenshots and recordings in the run directory.

How do I avoid port conflicts between parallel test environments?▼

Use the claim-isolated-port-range.sh script, which reserves a full 20-port block via lock directories in the shared git common dir. This prevents different worktrees from racing each other for the same ports.

Can I reuse a browser testing agent for retests after a fix?▼

Yes. Browser child agents are designed to be long-lived and accept follow-up instructions via agent_reply, such as retesting the same path after a fix, rerunning specific steps, or recording a final demo of the happy path.

Why does my isolated server show the main clone instead of the worktree?▼

The start script returns early if a healthy process already occupies the port, so an old server from the main clone may still be running. Stop it with stop-sandbox.sh, then restart with the --worktree flag pointing at your worktree.

When should I delete an isolated test run directory?▼

Only delete a run directory when explicitly asked for cleanup. Use stop-isolated-birdhouse.sh to halt the server while preserving artifacts, and trash-isolated-run.sh to close browser sessions, release the port lock, and remove the entire run directory.