메뉴
Automated code shipping pipeline — validate, integrate, version, publish, verify. USE WHEN ship, ship it, deploy, push to main, merge and deploy, create PR, land this branch, release, ship dry run, rollback, init ship config, setup shipping.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see AnalyticsTracking. USE WHEN ab test, split test, experiment setup, A/B test, multivariate.
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see AbTestSetup. USE WHEN analytics, tracking, GA4, measurement, Google Analytics.
Structure raw ideas into articulate outlines using Dan Koe's frameworks. USE WHEN articulate, structure ideas, outline talk, outline article, think through piece, brainstorm structure, how should I say this, organize my thoughts, structure this post, help me outline.
Balaji Srinivasan slide design system. USE WHEN balaji slides, balaji style, evidence slides, balaji presentation, split layout slides, create balaji deck, artifact-driven slides.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' USE WHEN competitor, alternatives page, vs page, comparison.
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' USE WHEN edit copy, proofread, copy review, grammar check.
| name | Ship |
| description | Automated code shipping pipeline — validate, integrate, version, publish, verify. USE WHEN ship, ship it, deploy, push to main, merge and deploy, create PR, land this branch, release, ship dry run, rollback, init ship config, setup shipping. |
Automated code shipping pipeline. One command to go from feature branch to merged PR with validation, review, versioning, and changelog. Project-configurable via .ship.json.
Inspired by gstack's /ship but adapted for PAI's architecture with configurable soft constraints.
Before executing, check for user customizations at:
~/.claude/skills/PAI/USER/SKILLCUSTOMIZATIONS/Ship/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
When executing a workflow, do BOTH:
Send voice notification:
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow in the Ship skill to ACTION"}' \
> /dev/null 2>&1 &
Output text notification:
Running the **WorkflowName** workflow in the **Ship** skill to ACTION...
| Workflow | Trigger | File |
|---|---|---|
| Ship | "/ship", "ship it", "ship this", "land this branch", "deploy this" | Workflows/Ship.md |
| ShipDryRun | "/ship --dry-run", "ship dry run", "simulate ship", "what would ship do" | Workflows/ShipDryRun.md |
| ShipRollback | "rollback", "revert last ship", "undo deploy", "ship rollback" | Workflows/ShipRollback.md |
| ShipInit | "init ship", "setup ship config", "create .ship.json", "ship init" | Workflows/ShipInit.md |
The pipeline is configured per-project via .ship.json in the project root.
{
// REQUIRED
"testCommand": "bun test", // Must exit 0 to pass
// BUILD (optional)
"buildCommand": null, // Pre-ship build step
// VERSIONING (optional)
"versionFile": "package.json", // Path to version file
"versionStrategy": "none", // semver-patch | semver-minor | calver | none
// CHANGELOG (optional)
"changelogFile": null, // Path to CHANGELOG.md
"changelogFormat": "none", // keep-a-changelog | git-log | none
// REVIEW (defaults on)
"reviewEnabled": true, // Show diff summary before pushing
"reviewMode": "full", // full | quick | skip
// PR / MERGE
"prEnabled": true, // Create PR (false = direct merge)
"protectedBranches": ["main"], // Branches that always require PR
"autoMergeMain": true, // Merge main into branch before ship
"baseBranch": "main", // Target branch
// DEPLOY (optional)
"deployCommand": null, // Post-merge deploy command
"healthCheckUrl": null, // URL to verify after deploy (must return 2xx)
"healthCheckTimeout": 30, // Seconds to wait for health check
// HOOKS (optional)
"preShipHook": null, // Command before pipeline starts
"postShipHook": null // Command after successful ship
}
All fields except testCommand are optional. Use /ship init to auto-generate.
PREFLIGHT → INTEGRATE → VALIDATE → REVIEW → VERSION → DOCUMENT → PUBLISH → VERIFY → [ROLLBACK]
Example 1: Ship a feature branch
User: "/ship"
→ Loads .ship.json
→ Merges main, runs tests, shows diff, bumps version, creates PR
→ Reports PR URL
Example 2: Check before shipping
User: "/ship --dry-run"
→ Runs full pipeline in read-only mode
→ Reports what WOULD happen, surfaces blockers
Example 3: Setup for a new project
User: "ship init"
→ Detects project type
→ Generates .ship.json with sensible defaults
→ Asks confirmation before writing
Example 4: Something went wrong
User: "rollback last ship"
→ Creates revert commit
→ Pushes revert
→ Reports status