Ship Deploy

Deploy the current worktree branch by merging to the main repository, following the repo's deployment workflow.

Workflow Discovery

This skill dynamically discovers how to deploy based on repo documentation:

1. Find Deployment Docs

Check for deployment documentation in order:

•docs/dev/deployment.md
•DEPLOYMENT.md
•CLAUDE.md (look for deployment section)

If found, parse for:

•Workflow type: direct (merge to master) or pr (pull request)
•Host repo path: Where the main repo lives (for direct workflow)
•Pre-merge checks: Commands to run before merging
•Post-merge steps: Commands to run after merging

2. Detect Build System

Infer test/lint commands from build system:

Build System	Test Command	Lint Command
Makefile	`make test`	`make lint`
package.json	`npm test`	`npm run lint`
Gemfile	`bundle exec rspec`	`bundle exec rubocop`

If no build system found, warn and skip automated checks.

3. Determine Workflow

If deployment docs found with type: direct:

•Follow direct-to-master workflow (merge, post-merge steps, push)

If deployment docs found with type: pr or no docs found:

•Fall back to PR workflow

Direct Workflow

When deployment docs specify direct workflow:

1. Pre-flight Checks

bash

# Must be clean
git status --porcelain  # Should be empty

# Run pre-merge checks from deployment docs
# Or infer from build system

2. Merge to Main Repo

bash

cd <host-repo-path>  # From deployment docs
git checkout <main-branch>
git pull origin <main-branch>
git merge <worktree-branch> --no-edit

3. Post-Merge Steps

Run commands from deployment docs (e.g., make init, make install, etc.)

4. Push and Rebase

bash

git push origin <main-branch>
cd <worktree-path>
git rebase <main-branch>

5. Note Deployment

The shipment remains in "in-progress" status. Deployment is tracked by the merge to master, not a separate status transition.

PR Workflow (Fallback)

When no deployment docs found or workflow type is pr:

1. Pre-flight Checks

bash

git status --porcelain  # Must be clean

Run any discovered test/lint commands (warn if none found).

2. Create Pull Request

Check for PR creation skill first, then fall back to gh CLI:

bash

# If gh CLI available
gh pr create --fill

3. Output

code

No deployment docs found. Using PR workflow.

Created PR: <url>

Follow your repository's review and merge process.

Build System Detection

bash

# Check for build systems in order
if [ -f "Makefile" ]; then
    TEST_CMD="make test"
    LINT_CMD="make lint"
elif [ -f "package.json" ]; then
    TEST_CMD="npm test"
    LINT_CMD="npm run lint"
elif [ -f "Gemfile" ]; then
    TEST_CMD="bundle exec rspec"
    LINT_CMD="bundle exec rubocop"
else
    echo "Warning: No build system detected. Skipping automated checks."
fi

Success Output

Direct workflow:

code

Deployed via direct workflow:
  - Branch merged to <main-branch>
  - Post-merge steps completed
  - Pushed to origin
  - Worktree rebased
  - Ready to close shipment

Run /ship-complete to close the shipment.

PR workflow:

code

Created pull request:
  - PR: <url>
  - Follow your repo's review process
  - After PR merges, run /ship-complete to close the shipment

Error Handling

Error	Action
Dirty working tree	List uncommitted files, ask to commit or stash
Pre-merge checks fail	Show failures, do not proceed
Merge conflicts	Report conflicts, do not auto-resolve
No gh CLI for PR	Provide manual instructions
Push rejected	Check if remote has new commits