skills.rest
Claudfather
ClaudfatherOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ship

Commits verified changes and opens pull requests via git and GitHub CLI.

Updated May 3, 2026
Search Tags:#git#code review#pull request#commit#conventional commits#rebase#github cli
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill ship-claudfather
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/ship
Command: npx skills add https://github.com/Claudfather/clauDNA --skill ship-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Landing code changes safely requires many error-prone steps — reviewing diffs, running tests, rebasing onto the base branch, writing good commit messages, and opening well-formed pull requests. This Skill enforces that discipline so nothing ships unverified or with sloppy history. ## Core Features & Use Cases - Commit mode: Stage explicitly named files, run tests/lint/type-checks, and create a conventional-commits checkpoint without opening a PR. - PR mode (default): Rebase onto the base branch, verify the full test suite, review the diff, bump versions, push, and open a structured pull request with gh pr create. - Anti-rationalization guardrails: Built-in red-flag checks stop common shortcuts like git add -A, vague commit messages, and skipping tests. - Use Case: After finishing a feature branch, say "ship" to rebase onto main, run the full verification suite, review the diff, and open a PR with a summary, test plan, and reviewer notes. ## Quick Start Ask the assistant to ship the current branch as a pull request, or say "commit" for a local checkpoint only.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I create a pull request from the command line?▼

Use the GitHub CLI with `gh pr create` after pushing your branch. This Skill automates the full flow: rebase onto the base branch, run tests, commit with a conventional message, push, and open a PR with a summary and test plan.

How to write good conventional commit messages?▼

Start with a type prefix like feat:, fix:, refactor:, docs:, test:, or chore:, then describe the change in imperative mood ("Add feature" not "Added feature"). Read the diff first so the message accurately describes what changed.

Does this Skill merge the pull request automatically?▼

No, it explicitly does not merge. It opens the PR and returns the URL, leaving the merge decision to the user. If any step fails along the way, it stops and reports the issue.

Why should I avoid git add -A when committing?▼

git add -A stages everything, including .env files, editor auto-saves, and leftover debug code in unrelated files. Stage files explicitly by name after running git status and git diff so you know exactly what is being committed.

What tools are required to use the PR creation flow?▼

The PR mode requires the GitHub CLI (gh) for creating pull requests, plus git for staging, rebasing, committing, and pushing. Commit-only mode works with git alone.

Related Skills

Explore More Software Engineering Skills→
cursorcursor
2.6k

new-branch-and-pr

Create a feature branch from main and open a pull request.

Official
Intermediate
pcaokhaipcaokhai

ship

Merge base, run tests, bump version, update changelog, and create a pull request.

Community
Advanced
lemeblemeb

test

...

Community
Intermediate
howarewoohowarewoo

commit

Manage code commits and pull request updates with Graphite and GitHub CLI.

Community
Advanced