skills.rest
tak-bro
tak-broCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Verify code changes, commit with conventional messages, and create a pull request.

Updated Aug 27, 2026
Search Tags:#automation#git#verification#pr#ci-cd#ship
One-click install
npx skills add https://github.com/tak-bro/claude-code --skill ship-tak-bro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/tak-bro/claude-code/tree/main/skills/ship
Command: npx skills add https://github.com/tak-bro/claude-code --skill ship-tak-bro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push code that has passed all validations and create a PR.

Core Features & Use Cases

  • Final verification: run tests and lint, ensure build success.
  • Commit & Push: create commits with conventional messages and push to feature branches, not main.
  • PR Description Generation: auto-generate a draft PR description including summary of changes, test results, and testing steps.
  • Safety guardrails: ensures not to push to main; prompts user before PR creation.
  • Workflow: Phase 1: Final Verification; Phase 2: Commit & Push; Phase 3: PR Description Generation.

Quick Start

Run the ship workflow to push validated changes and create a PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git commit, push, and PR creation after passing tests?▼

To automate push and PR creation, the workflow runs final verification checks like tests and lint, commits validated code with conventional messages to a feature branch, and auto-generates a draft PR description including test results and testing steps.

Can I use this to prevent accidental git pushes to the main branch?▼

Yes, the workflow enforces safety guardrails that explicitly prevent pushing directly to the main branch, ensuring validated changes are only committed to feature branches before prompting you for PR creation.

How does auto-generated PR description work for validated code changes?▼

The PR description generation automatically creates a draft that includes a summary of your code changes, the final verification test results, and step-by-step testing instructions for reviewers.

What is the best way to enforce CI/CD safety rules before merging code?▼

The best way is to enforce a three-phase workflow: run final verification for tests and lint, commit and push to non-main feature branches, and generate a draft PR description to ensure all changes pass safety checks before merging.

Does this workflow support conventional commit messages for feature branches?▼

Yes, the commit and push phase automatically creates commits using conventional messages and pushes them exclusively to feature branches, preventing any direct pushes to the main branch.

Why should I use an automated workflow for PR creation instead of manual git commands?▼

Using an automated workflow ensures code changes pass final verification like tests and lint before merging, enforces safety guardrails against main branch pushes, and saves time by auto-generating draft PR descriptions with testing steps.

Related Skills

Explore More Software Engineering Skills→
googlegoogle
291

Push to GitHub

Run unit tests and lint checks before pushing changes to GitHub.

Official
Intermediate
omerakbenomerakben
1

git-workflow-deployment

Automate Git branching, CI/CD gates, and Vercel production deployments.

Community
Intermediate
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
udecodeudecode
1.2k

drafting-pr

Create and update GitHub draft pull requests with conventional commits.

Official
Intermediate