PathToShip: production readiness for AI-built apps
com.pathtoship/pathtoship
Tools
Exactly what the server advertised in the scan completed . Effects and capabilities are classified by Squatch from each tool's metadata. Squatch never runs tools.
- Effect: Read 5
- Effect: Write 3
Showing 8 of 8 tools
| Details | ||
|---|---|---|
| prr_interview Record the launch facts no scanner can see — backups restored, rollback rehearsed, on-call, database tier, largest table, last month's bill… | Effect: Write | |
| start_scan Check whether this app is safe to launch for real users — finds the security, scalability, and production-readiness problems that break lau… | Effect: Write | |
| verify_fix Confirm your fixes actually resolved the problems: re-checks the repository and reports resolved, still open, and newly introduced. Run aft… | Effect: Write | |
| check_connection Check whether PathToShip is connected for this account and, if you name a repository, whether it can reach it — use when a check says INSTA… | Effect: Read | |
| get_finding_detail Explain one production risk and exactly how to fix it for this app's stack. | Effect: Read | |
| get_findings List what would hurt this app in production, worst first. Compact — one line per problem; use get_finding_detail for how to fix one. | Effect: Read | |
| get_scan_status Check whether a readiness check has finished. | Effect: Read | |
| get_score Is this app ready to ship? The readiness score, the ship bar, the weakest area, and what this stack will cost at 10x users. | Effect: Read |