nathanghart/pathtoship
Production-readiness checks for AI-built apps: scan the repository your builder syncs to, fix what would break, and verify the fix landed.
Add the PathToShip readiness badge to the README and the app's site once a scan clears the ship bar. Use when get_score or verify_fix returns verdict "ready", or when the user asks to show their readiness score or credential.
Keep a launch-readiness record in the repository — which PathToShip checks ran on which commit, what was found, fixed, or accepted, and the operational items no scanner can see. Use after a verify_fix, before a launch or client handoff, or when asked for an audit trail of readiness.
Run a PathToShip production-readiness check before deploying, exposing a public URL, or handling real user data, then drive the scan → fix → verify loop. Use when the user mentions launching, deploying, going live, shipping, adding auth/payments/uploads, or asks whether the app is ready or safe.