Code Ship & PR Automator FAQs

Question 1

Does the Ship skill automatically merge failing code?

Accepted Answer

No, the skill performs a readiness check by running project tests and monitors CI status. It only proceeds with the merge if all checks pass, preventing broken code from reaching the main branch.

Question 2

Can it handle custom GitHub PR templates?

Accepted Answer

Yes, it automatically detects pull request templates in your .github directory and populates them with summaries of your changes and test plans.

Question 3

Does it delete branches after a successful merge?

Accepted Answer

Yes, the skill includes a post-merge verification step that cleans up local and remote feature branches and pulls the latest updates from the main branch.

Question 4

How does it protect against committing sensitive information?

Accepted Answer

The skill is configured to ignore common secret-bearing files like .env and credentials, and it will warn you if it detects such files in the working tree during the staging process.

Question 5

Can I use it for routine commits without opening a PR?

Accepted Answer

The Ship skill is specifically designed for full delivery phases. For routine, incremental commits, it is recommended to use a standard commit skill or git directly.

Code Ship & PR Automator

주요 기능

사용 사례

Code Ship & PR Automator

주요 기능

사용 사례