ship-it

Étoiles10

Forks0

Mis à jour10 juillet 2026 à 16:32

This skill should be used when the user asks to "commit and push", "commit push and PR", "create a PR for this", "open a pull request for this", "ship this change", "ship it", ":rocket:", or otherwise wants edited code committed, pushed to the remote, and turned into a pull request in one flow.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

kelsin

kelsin/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	ship-it
description	This skill should be used when the user asks to "commit and push", "commit push and PR", "create a PR for this", "open a pull request for this", "ship this change", "ship it", ":rocket:", or otherwise wants edited code committed, pushed to the remote, and turned into a pull request in one flow.
version	0.2.0

Ship It

Run the full flow autonomously by invoking four sub-skills in sequence: commit, rebase, push, then open a PR. Do not pause for confirmation between steps unless genuinely blocked (e.g. a sub-skill stops with an error, no clean way to proceed).

Step 1: Commit

Invoke the commit-changes skill. If it stops (e.g. nothing to commit, failing tests, secrets detected), stop here and surface its report — do not proceed to Step 2.

Step 2: Rebase

Invoke the rebase-branch skill to sync the branch onto the latest default branch before pushing. If it stops (e.g. unresolvable conflict, diverged branch), stop here, surface its report, and ask the user how to proceed — do not proceed to Step 3.

Step 3: Push

Invoke the push-changes skill. Because Step 2 just rebased the branch, this push will force-push (--force-with-lease) — that's expected and doesn't need separate confirmation. If it stops (e.g. push rejected), stop here and surface its report — do not proceed to Step 4.

Step 4: Open or reuse the PR

Invoke the create-pr skill and report the resulting PR URL back to the user.

Notes

Never plain force-push (--force), skip hooks (--no-verify), or bypass signing. --force-with-lease after the Step 2 rebase is expected, per the push-changes skill.
Never use destructive git operations (reset --hard, clean -f) as part of this flow.
If any sub-skill fails, stop and surface the actual error rather than working around it silently.

Plus depuis ce dépôt

même dépôt

cleanup-branch

kelsin/dotfiles

This skill should be used when the user asks to "clean up this branch", "clean up my branch", "delete this branch", "I'm done with this PR", "I'm done with this", "that's done" / "that wraps this up" / "all set here" (said about the current branch/PR work), or otherwise wants the local branch for a PR removed once that PR is closed/merged, followed by checking out the default branch and pulling the latest changes. Only deletes the LOCAL branch — never touches the remote branch or the PR itself.

2026-07-1010

rebase-branch

kelsin/dotfiles

This skill should be used when the user asks to "rebase this", "rebase my branch", "rebase onto main", "pull latest and rebase", "sync my branch with main/default", or otherwise wants their branch updated with the latest remote state and replayed on top of the latest default branch. Resolves conflicts automatically when safe, otherwise asks the user. After it completes, the push-changes skill can safely force-push the result. Also used internally by the ship-it skill as its second step, between commit and push.

2026-07-1010

create-pr

kelsin/dotfiles

This skill should be used when the user asks to "open a PR", "create a PR for this", "open a pull request for this", "update the PR", "sync the PR description", or otherwise wants a pull request opened, reused, or refreshed with new pushed commits for the current branch, which must already be pushed to the remote. Also used internally by the ship-it skill as its fourth step.

2026-07-1010

commit-changes

kelsin/dotfiles

This skill should be used when the user asks to "commit this", "commit my changes", or otherwise wants edited code checked for safety and committed locally (without pushing or opening a PR). Also used internally by the ship-it skill as its first step.

2026-07-1010

push-changes

kelsin/dotfiles

This skill should be used when the user asks to "push this", "push my branch", or otherwise wants local commits pushed to the remote (without opening a PR). Also used internally by the ship-it skill as its third step (after rebase-branch), and after the rebase-branch skill to land a rebased branch.

2026-07-1010

name	ship-it
description	This skill should be used when the user asks to "commit and push", "commit push and PR", "create a PR for this", "open a pull request for this", "ship this change", "ship it", ":rocket:", or otherwise wants edited code committed, pushed to the remote, and turned into a pull request in one flow.
version	0.2.0

Ship It

Step 1: Commit

Invoke the commit-changes skill. If it stops (e.g. nothing to commit, failing tests, secrets detected), stop here and surface its report — do not proceed to Step 2.

Step 2: Rebase

Step 3: Push

Step 4: Open or reuse the PR

Invoke the create-pr skill and report the resulting PR URL back to the user.

Notes

Never plain force-push (--force), skip hooks (--no-verify), or bypass signing. --force-with-lease after the Step 2 rebase is expected, per the push-changes skill.
Never use destructive git operations (reset --hard, clean -f) as part of this flow.
If any sub-skill fails, stop and surface the actual error rather than working around it silently.