ship

Dispatch pre-ship validation tasks to code review, security audit, and test coverage subagents.

Updated May 27, 2026
One-click install
npx skills add https://github.com/santanapol/agent-skills --skill ship-santanapol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/santanapol/agent-skills/tree/main/.cursor/skills/ship
Command: npx skills add https://github.com/santanapol/agent-skills --skill ship-santanapol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual pre-launch checks are time-consuming, inconsistent, and often miss critical issues across code quality, security, and test coverage, leading to failed production deployments or security incidents.

Core Features & Use Cases

  • Parallel Fan-out Validation: Automatically dispatches specialized subagents (code-reviewer, security-auditor, test-engineer) to run comprehensive checks in parallel, with a sequential fallback if parallel execution is unavailable.
  • Unified Go/No-Go Decision: Aggregates findings from all subagents into a single actionable decision, including categorized blockers, recommended fixes, acknowledged risks, and a detailed rollback plan.
  • Use Case: Before shipping a new payment processing feature, use this skill to automatically validate code quality, scan for OWASP vulnerabilities and exposed secrets, and check test coverage gaps, then get a clear go/no-go verdict with rollback steps if issues are found.

Quick Start

Use the ship skill to run a full pre-launch audit of your current code changes and get a go/no-go decision with a rollback plan before shipping to production.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate pre-ship checks for a go/no-go production deployment decision?

Automated pre-ship checks run parallel fan-out validation tasks to specialized code review, security audit, and test coverage subagents, aggregating findings into a unified go/no-go decision with rollback planning.

What is the best way to scan code changes for OWASP vulnerabilities and exposed secrets before launch?

Scanning for OWASP vulnerabilities and exposed secrets before launch is handled by dispatching a specialized security auditor subagent in parallel with other pre-ship validation tasks to identify risks.

How do I run parallel code review and test coverage checks without manual intervention?

Parallel code review and test coverage checks run by automatically fanning out tasks to specialized subagents, with a sequential fallback if parallel execution is unavailable in your environment.

Does this pre-ship validation process generate a rollback plan for failed production deployments?

Yes, pre-ship validation generates a detailed rollback plan by aggregating cross-specialist findings, categorizing blockers, and providing risk mitigation steps alongside the final launch decision.

Can I use this launch orchestration skill for infrastructure configuration validation?

Yes, you can use this launch orchestration for infrastructure configuration validation, as it applies to software development workflows requiring comprehensive pre-ship checks across code, security, and infrastructure.

When should I not use an automated go/no-go decision for shipping features?

You should not use an automated go/no-go decision when your software development workflow falls outside standardized pre-ship validation needs, as the skill targets auditable launch checks for code, security, and coverage.