ship-it

Automate CI/CD deployments with quality gates, canary traffic, and rollback.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Mrjoel97/PIKAR-AI --skill ship-it-mrjoel97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/Mrjoel97/PIKAR-AI/tree/main/skills/ship-it
Command: npx skills add https://github.com/Mrjoel97/PIKAR-AI --skill ship-it-mrjoel97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the risky, multi-step process of taking local code changes through verification, migration, PR workflow, and deployment so teams can release safely and reliably without missing quality gates or rollback protections.

Core Features & Use Cases

  • Full CI/CD Orchestration: Scans changes, runs parallel quality gates (lint, type-check, tests), stages and commits fixes, and creates PRs with structured summaries.
  • Safe Database Migration Flow: Uses the Supabase MCP workflow to list projects/migrations, validate SQL, apply migrations, run security and performance advisors, and remediate blockers before deployment.
  • Canary Deploy + Verification: Deploys backend to Cloud Run with traffic splits (10% → 50% → 100%), deploys frontend to Vercel, captures pre- and post-deploy performance baselines, verifies health endpoints, and performs automated rollback after retry limits.
  • Use Case: Run when a developer says "ship it" or requests a one-shot release to move local changes (including migrations) into production while ensuring minimal risk and automated remediation.

Quick Start

Ask the assistant to "ship it" to run the full CI/CD pipeline from scan through canary deploys, verification, and automatic rollback if needed.

Frequently Asked Questions about ship-it

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

FAQPage Schema
How do I automate end-to-end CI/CD deployments for Vercel and Cloud Run?

Automate end-to-end CI/CD deployments by scanning git changes, running parallel quality gates, applying Supabase migrations, and executing canary traffic splits on Cloud Run with Vercel frontend deploys. This orchestrates the full release pipeline from local code to verified production.

How do Supabase migrations work during an automated production deployment?

Supabase migrations during deployment use the Supabase MCP workflow to list projects, validate SQL, apply changes, and run security and performance advisors. The workflow automatically remediates blockers before proceeding to canary deployment.

Can I use canary traffic splitting for backend deployments on Cloud Run?

Canary traffic splitting for backend deployments on Cloud Run is supported by routing traffic incrementally at 10%, 50%, and 100%. The pipeline verifies health endpoints and captures performance baselines at each stage before full promotion.

What happens if a canary deployment fails health checks on Cloud Run?

If a canary deployment fails health checks on Cloud Run, the pipeline performs an automated rollback after retry limits are exceeded. It captures pre-deploy and post-deploy performance baselines to verify health endpoints and trigger rollback safely.

Does the deployment pipeline run linting and tests before creating a Pull Request?

The deployment pipeline runs parallel quality gates including linting, type-checking, and tests before staging fixes and creating a Pull Request. Structured summaries are generated automatically to ensure quality gates are passed prior to merging.

Do I need to manually check environment variables before deploying to Vercel and Supabase?

Manual environment variable checks are unnecessary because the pipeline performs environment variable diffing automatically. This verifies configuration consistency across Vercel and Supabase before applying migrations and executing production releases.