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 a README or site after 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.
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 on a GitHub repository and, within the scope the user has authorized, drive the scan → fix → verify loop. Use when the user asks whether their app is ready to launch or safe for real users, or asks for a readiness check as part of a launch or deploy they are working on.