Ship Changes

What it does

When your agent uses it

• Finishing a piece of work and wanting it committed, pushed and opened as a PR
• Reviewing exactly which files and message will be committed before anything is staged
• Opening a PR with a drafted title, summary and test plan

Example prompts

• “I'm done with the login fix. Ship it.”
• “Commit these changes, push the branch and open a PR, but let me approve each step.”
• “Check what has changed, propose the files to stage and draft a commit message.”

Requirements

• A git repository with changes to ship
• The `gh` command-line tool for the pull request step
• Pre-approved tools (allowed-tools): Bash(git status), Bash(git diff *), Bash(git log *), Bash(git add *), Bash(git commit *), Bash(git push *), Bash(git checkout *), Bash(git branch *), Bash(gh pr create *), Bash(gh pr view *), Bash(git fetch *), Bash(git for-each-ref *)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Scan
2. 2Stage & Commit
3. 3Push
4. 4Pull Request
5. 5Branch cleanup (optional)

What it can do on your machine

Read from SKILL.md and the folder at commit 94b84b9. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash(git status)
  • Bash(git diff *)
  • Bash(git log *)
  • Bash(git add *)
  • Bash(git commit *)
  • Bash(git push *)
  • Bash(git checkout *)
  • Bash(git branch *)
  • Bash(gh pr create *)
  • Bash(gh pr view *)

  …and 2 more on the same allowed-tools line.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • gh

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ship Changes loads about 953 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 483 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~34

When it runs · the whole SKILL.md, loaded when a task matches

~953

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:43

  - Secrets: `.env*`, `*.pem`, `*.key`, `credentials.json`

• NoteMentions a .env fileSKILL.md:85

  - NEVER commit .env, secrets, or credential files

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from poshan0126/dotclaude at commit 94b84b9, republished under its MIT licence (© poshan0126). 483 words, ~953 tokens.

name

ship

description

Commit, push, and create a PR for staged changes, with confirmation at each step. Use when your work is done and you want to ship.

allowed-tools

Bash(git status), Bash(git diff *), Bash(git log *), Bash(git add *), Bash(git commit *), Bash(git push *), Bash(git checkout *), Bash(git branch *), Bash(gh pr create *), Bash(gh pr view *), Bash(git fetch *), Bash(git for-each-ref *)

argument-hint

[optional commit message or PR title]

disable-model-invocation

true

© poshan0126, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ship of poshan0126/dotclaude.

Open the folder on GitHubat commit 94b84b9