ship-check

Audit SEO, payment flows, error handling, and security configurations for production readiness.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/koach08/claude-code-skills --skill ship-check-koach08
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-check
Source: https://github.com/koach08/claude-code-skills/tree/main/skills/development/ship-check
Command: npx skills add https://github.com/koach08/claude-code-skills --skill ship-check-koach08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents common production failures by automating the verification of critical launch requirements like SEO, payment flows, and security configurations.

Core Features & Use Cases

  • Multi-Domain Verification: Checks SEO metadata, OG images, and social sharing tags to ensure optimal discoverability.
  • Production Readiness: Validates payment integrations, error handling, analytics, and security headers before deployment.
  • Use Case: Before pushing a new SaaS update to production, run this skill to ensure no test API keys remain and that all critical error boundaries and analytics trackers are correctly configured.

Quick Start

Run the ship-check skill to verify the production readiness of the current project directory.

Frequently Asked Questions about ship-check

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

FAQPage Schema
How do I verify production readiness for a SaaS web application before deployment?

Production readiness verification audits SEO metadata, payment flows, error handling, and security configurations to ensure all critical infrastructure is correctly configured. It checks source files and environment configurations to validate API keys and build settings.

What should a pre-deployment checklist include for SaaS products?

A pre-deployment checklist for SaaS products should include multi-domain verification of SEO tags, OG images, payment integrations, error boundaries, analytics trackers, and security headers to prevent common production failures and ensure optimal discoverability.

How do I check if my project source files still contain test API keys before launching?

Checking for test API keys requires scanning project source files and environment configurations to validate metadata and build settings. This automated verification ensures no test API keys remain before pushing a SaaS update to production.

Can I audit SEO metadata and security configurations automatically for a web project?

Auditing SEO metadata and security configurations automatically validates social sharing tags, OG images, and security headers within the project directory. It ensures optimal discoverability and correct infrastructure setup before deployment.

Does this production checklist require access to specific project files?

This production checklist requires access to project source files and environment configurations. It validates metadata, API keys, and build settings by running directly within the current project directory to verify launch requirements.

When do I need to run an error handling and analytics verification check?

Error handling and analytics verification is needed before pushing a new SaaS update to production. It ensures all critical error boundaries and analytics trackers are correctly configured to prevent common production failures post-launch.