ship

Automate browser-based QA and design-review workflows with Playwright.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shaneholloman/ship --skill ship-shaneholloman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/shaneholloman/ship/tree/main
Command: npx skills add https://github.com/shaneholloman/ship --skill ship-shaneholloman

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ship provides a fast headless browser and a suite of QA/design/documentation workflows to verify, document, and iterate on web apps without manual browser toil.

Core Features & Use Cases

  • Persistent headless browser for QA testing and dogfooding.
  • Snapshot-based element refs and diffing to verify changes.
  • Automated documentation updates and design workflows.
  • Quick-start examples to validate features quickly.

Quick Start

Open a terminal and run a sample workflow like /plan-review-founder to see the browser-powered QA in action.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate headless browser QA testing for web applications?

Automate headless browser QA testing by running a persistent Playwright browser via Bun, using snapshot-based element refs and commands like goto, click, and screenshot to verify web app changes.

What is snapshot-based element diffing in Playwright?

Snapshot-based element diffing captures references of web page elements through Aria commands, allowing you to compare browser states and verify UI changes without manual visual inspection.

Do I need Bun installed to run Playwright headless browser workflows?

Yes, Bun is required as the runtime environment. The headless browser workflows rely on Bun to execute Playwright commands and maintain the preamble-driven session model for QA tasks.

Can I automate documentation updates using a headless browser?

Yes, you can automate documentation updates by navigating web apps with a persistent headless browser, capturing screenshots, and verifying design workflows to generate accurate docs.

How do I start a design-review workflow for dogfooding web apps?

Start a design-review workflow by running a sample command like /plan-review-founder in your terminal, which triggers the headless browser to execute QA and snapshot verification.

What are the limitations of using a headless browser for design review?

Headless browser design reviews rely on Aria snapshot refs and may not capture visual rendering nuances perfectly, requiring manual verification for complex CSS layout regressions.