Ship: CI/CD & PR Automator FAQs

Question 1

What happens if a CI check fails during the ship process?

Accepted Answer

The skill monitors CI status; if a blocker is detected, it informs the user, surfaces the failure logs, and allows for fixes before resuming the ship workflow.

Question 2

Can it handle existing GitHub PR templates?

Accepted Answer

Yes, the skill searches for PULL_REQUEST_TEMPLATE.md files in the .github directory and populates them automatically with implementation summaries and test plans.

Question 3

Does it support automatic branch cleanup?

Accepted Answer

Yes, after a successful merge, the skill handles post-merge cleanup by deleting the local and remote feature branches and pulling the latest changes from the main branch.

Question 4

Does the Ship skill run tests before creating a PR?

Accepted Answer

Yes, the skill automatically identifies and executes project-specific test and build commands to ensure code integrity before any staging or PR creation occurs.

Question 5

Can I resume a ship process if Claude is restarted?

Accepted Answer

Yes, the skill utilizes a .workflow-state.json file to track progress, allowing it to resume from the specific step where it left off, such as monitoring a pending PR.

Ship: CI/CD & PR Automator

Key Features

Use Cases

Ship: CI/CD & PR Automator

Key Features

Use Cases