S Shipwright

Launch QA for vibe-coded projects

Before you ship the AI-built app, make it survive first contact.

Paste a GitHub repo or demo URL. Shipwright generates a launch-readiness report in seconds — browser health, README friction, fake-complete features, and the next fixes that matter.

Try a sample:
Read the guide · View on GitHub
10
reusable skills
10 min
first report target
0
fake green checks

Choose the job

Four doors. One clean launch path.

Shipwright is no longer just a pretty audit page. Pick the work you need now: shape an idea, inspect a project, install reusable skills, or run the full agent workflow.

01 Audit a repo or demo

Paste a GitHub URL or live demo and get a launch-readiness report with the next patch.

Run launch QA 02 Plan from a rough idea

Let the AI Planner ask follow-up questions and turn a vague website concept into a buildable plan.

Start with an idea 03 Ship with a sequence

Move from agent claims to browser proof, install proof, release copy, and public launch.

See workflow 04 Install the workflow

Use the open-source skills inside Codex or Claude Code for evidence-backed local checks.

Browse skills

The pain

AI agents are great at producing finished-looking work.

01

The README lies by omission.

It says "npm install" but forgets env vars, version constraints, and what success looks like.

02

The browser was never opened.

Console errors, broken routes, missing assets, and mobile overflow hide behind a clean diff.

03

The launch page has no sharp promise.

Strangers need a quickstart, proof, limitations, and GitHub metadata before they trust it.

Try it now

Generate a launch QA report.

Paste any GitHub repo URL or owner/repo. Doctor calls the GitHub public API directly from your browser, analyzes the README, and produces a fix plan you can paste into Claude Code or Codex. Nothing is sent to any server.

Try a sample:
Launch channel

Detecting mode… Enhanced mode runs richer GitHub checks via the Doctor backend (CI/CD, SECURITY, package.json, URL probe). If the backend is unreachable from your network it falls back to in-browser checks automatically.

Paste a repo URL and click Analyze to generate your launch QA report.

What does Shipwright actually check?

Agent output review

  • Hallucinated feature claims
  • Fake buttons and dead links
  • TODO / FIXME / placeholder strings
  • Unverified integration references

Browser launch audit

  • Console errors and warnings
  • Network 4xx/5xx failures
  • Interactive element functionality
  • Mobile layout at 390px and 768px

README install audit

  • Missing env vars or API keys
  • Version constraint gaps
  • Expected output not shown
  • First-run path ambiguity

GitHub release checklist

  • Repo topics and description
  • Release notes completeness
  • Launch post copy quality
  • Contributor-facing next issues

Beyond the code check

Does your site match what you actually want?

The Audit on the left tells you whether the code ships. This wizard tells you whether the vibe, content, and audience match what you're really building. Uses your AI Planner key — runs in your browser.

  1. 1 Project
  2. 2 Audience
  3. 3 Goal
  4. 4 Vibe
  5. 5 Feels
What are you building?
Project type
Stage
Who is this for?
Primary audience (pick all that apply)
How technical are they?
What's the primary goal of this site?
Pick the single most important outcome
What should it feel like?
Brand vibes (pick 1–3)
How does it feel right now?

5 questions · ~60 seconds

Mission control · T-minus to launch

Take the report off the page. Ship it.

Pre-flight
  • Project URL / repo —
  • AI planner key —
  • Last audit score —
  • Brand fit answers —
Launch manifest
Tone

Generates release notes · Twitter thread · Reddit post in one AI call.

Standing by
Release notes will appear here after launch.
A 3–5 tweet thread will appear here.
A Reddit post draft will appear here.

Push release to GitHub

Token is stored in your browser only and sent only to api.github.com. Use a fine-grained PAT with Contents: Read & write on the target repo (or a classic token with repo scope). Create one →

Usage guide

Use Shipwright in two modes.

The website is the product demo and report builder. The installed skills are the real agent workflow for evidence-backed browser, README, and release audits.

01

Paste the thing you want to ship.

Use a GitHub repo, owner/repo, a localhost URL, or a public demo URL. Shipwright is built for web apps, skill packs, MCP servers, CLIs, and templates.

02

Generate the launch risk report.

Choose the project type and launch channels. The demo report shows the exact categories Shipwright checks: fake-complete work, browser health, install path, and GitHub packaging.

03

Turn findings into the next patch.

Copy or download the Markdown report, then give it to Codex or Claude Code as the fix plan before posting the project publicly.

Who is this for

Built for builders who ship fast and want it to actually work.

Vibe coders

You built it with Claude, Cursor, or Copilot in a weekend. Before you tweet the link, make sure it survives a stranger clicking "Get started."

Indie hackers

You're launching on Product Hunt next week. Shipwright catches the broken mobile layout and missing env vars before your first users do.

Open source maintainers

Your README says "easy setup" but a new contributor gives up at step 3. Shipwright walks the install path like a stranger and reports where it breaks.

AI skill / MCP authors

Your skill pack or MCP server looks done in the editor. Shipwright checks trigger descriptions, install paths, and security boundaries before publish.

Inspection radar

Plot the launch route before the public countdown.

A quiet control-room view of the checks Shipwright runs: each waypoint maps to a launch risk, the evidence it needs, and the fix signal a builder should trust.

Launch Map 04 Signal: evidence required
Evidence

Every green light needs an observed browser state, command output, or file reference.

Risk

Markers call out launch blockers before they become public support requests.

Patch

The route ends with the smallest next fix, not a vague quality score.

How it becomes real

From agent claim to proof.

1

Claim

Agent output review

Input

Repo, README, live URL, and the agent's finished-sounding claims.

Check

Catch hallucinated claims, fake buttons, TODOs, and unverified integrations.

Output artifact

P0/P1 findings list, dead-link inventory, and stripped fake-complete claims.

2

Open

Browser launch audit

Input

Live URL, primary CTA path, and the viewport widths people actually use.

Check

Open the app, check console/network health, interactions, mobile layout, and trust gaps.

Output artifact

Console proof, viewport notes, broken-state screenshots, and the next browser fix.

3

Install

README install audit

Input

Public quickstart, env setup, version requirements, and first-run commands.

Check

Follow the public install path like a stranger and record exactly where adoption breaks.

Output artifact

Missing-step log, expected output block, and a smaller patchable quickstart.

4

Package

GitHub release checklist

Input

Fixed findings, product promise, release diff, and one proof-led screenshot or report.

Check

Generate topics, description, release notes, launch post, and next contributor issues.

Output artifact

Release package, launch copy, contributor-facing issues, and a clean next patch.

Honest status

What this demo does and does not do.

This demo does

  • Generate a structured launch QA report based on project type
  • Show the exact audit categories the real skills check
  • Produce a copyable/downloadable Markdown report for your agent
  • Offer AI-powered website planning (BYOK — bring your own API key)

This demo does not

  • Clone your GitHub repository or read its files
  • Open a real browser to check console errors or mobile layout
  • Store your API key on any server (key stays in your browser only)
  • Make requests without your explicit API key configuration

For real, evidence-backed audits, install the open-source skills and run them locally with Claude Code or Codex.

All 10 skills

Install the workflow, not just the promise.

01

Discovery

Find what is worth building before you waste a launch slot.

Discovery

github-radar

Scan GitHub Trending and separate tools, opportunities, and hype traps.

Discovery

trend-to-product

Turn a hot repo or trend into a differentiated product opportunity.

02

Planning

Turn rough ideas into scoped work that can survive implementation.

Planning

idea-to-prd

Convert a rough idea into a lean PRD with scope and acceptance criteria.

Planning

prd-to-issues

Break a PRD into GitHub-ready issues ordered by delivery sequence.

03

QA

Run the checks that turn agent confidence into evidence.

QA

launch-readiness

Audit a project for README, install, demo, trust, and conversion gaps.

QA

browser-launch-audit

Verify a web app in a real browser before shipping.

QA

readme-install-audit

Test if a first-time user can install from the README alone.

QA

agent-output-review

Catch hallucinated or fake-complete AI-generated work.

04

Launch

Package the public release so the proof survives outside your repo.

Launch

github-release-checklist

Package a repo for public release with metadata and launch copy.

05

Meta

Turn one repeated launch ritual into an installable tool of your own.

Meta

workflow-to-skill

Turn a repeated workflow into a clean, installable skill.

AI-powered planning

Start messy. Leave with a build brief.

Tell the AI Planner your website idea. It asks targeted questions about users, features, proof, stack, and visual direction, then turns the answers into a complete website creation plan.

BYOK — key stays in localStorage and only calls your chosen API endpoint.
Ask Clarify the real user

Audience, pain, proof, constraints, and what the first visit must accomplish.

Shape Turn answers into scope

MVP features, page map, content blocks, design direction, and launch risks.

Review Send it through Shipwright

Use the generated brief as the input, then audit the finished site before sharing.

Open source first

Ship fewer beautiful half-products.

Start with the skills today. Turn this website into the hosted version when the workflow proves people keep coming back before every launch.

View on GitHub Try the demo

AI Planner Settings

Your API key is stored in your browser only (localStorage). It is never sent to any server other than the API endpoint you specify above.