ship

Orchestrate parallel subagent analysis for pre-merge code review and post-deployment verification.

4|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/highflame-ai/ai-factory --skill ship-highflame-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/ship
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill ship-highflame-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of shipping broken or unverified code by automating the pre-merge review process and post-deployment validation, ensuring that only high-quality, tested changes reach production.

Core Features & Use Cases

  • Parallel Specialist Review: Automatically fans out specialized subagents to analyze security, cross-repo impact, database migrations, and policy compliance simultaneously.
  • Post-Deploy Verification: Performs automated health checks on shared development environments using MCP tools or manual checklists to confirm successful rollouts.
  • Use Case: Before merging a complex PR that touches database migrations and authentication logic, use this Skill to run a comprehensive security and migration audit, synthesize the findings, and verify the deployment health after the merge.

Quick Start

Use the ship skill to perform a pre-merge analysis and post-deploy verification for the current pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate pre-merge code review for database migrations and security?

Automated pre-merge code review deploys parallel subagents to analyze database migrations, security vulnerabilities, and cross-repo impact simultaneously. This orchestrates specialized checks before merging, synthesizing findings to ensure only verified changes ship.

What is post-deployment verification in CI/CD pipelines?

Post-deployment verification in CI/CD pipelines performs automated health checks on shared development environments after rollout. It uses environment observability tools and manual checklists to validate deployment health and confirm rollback safety.

Does this automated code review work with cross-repo impact assessment?

Yes, automated code review fans out specialized subagents specifically for cross-repo impact assessment. This allows simultaneous analysis of policy compliance and security vulnerabilities across multiple repositories before merge.

How do I verify deployment health and rollback safety after a complex PR merge?

Verify deployment health after a PR merge by running automated post-deploy checks using MCP tools or manual checklists. This validates environment stability, confirms successful rollouts, and ensures rollback safety for shared development environments.

What's the best way to run a security and migration audit before merging?

The best way to run a security and migration audit before merging is orchestrating parallel specialist subagents. This approach simultaneously evaluates policy compliance, security risks, and database migration impacts, synthesizing findings into a comprehensive review.

Can I use MCP tools for automated health checks on shared development environments?

Yes, you can use MCP tools to perform automated health checks on shared development environments. These tools integrate with environment observability systems to validate deployment health, confirm successful rollouts, and ensure rollback safety.