Skip to content
Get packs

Ship a Change

Guides an agent through screenshots, changelog, tests, commit, push and publish for a finished change

Source Download skill
Repository
MengTo/Skills
Stars
7,187
Licence
MIT
Files
5 files

What it does

When installed, the agent follows a fixed end-of-change checklist for a game-style project: capture screenshots of the change, add a changelog entry, run tests, make one clean commit with only its own files, merge the latest main and push it as a fast-forward, publish that exact build live, and check the live site. It also measures the size of each commit, push and upload, and stops to ask you before anything over 50 MB goes out. Helper scripts do the size measuring and the safe push, and a post-publish check confirms the live pages and assets load.

Great for

  • Developers who run a game or web project with a git main branch and a live hosting site and want consistent release steps
  • Teams using several agent sessions on one shared checkout who need guardrails against overwriting others' work
  • Maintainers who want measured sizes reported with every commit and push

Skip it if

  • Projects without a git remote, changelog or live site, since most steps will not apply (the skill is built around one project's workflow)
  • Anyone wanting unattended pushes or deploys: the skill is designed to stop and ask for uploads over 50 MB, for force-pushes, and when permission checks block a deploy, and it can publish to a live site on your behalf
  • Repositories where the scripts' assumptions (macOS-style stat flags, pnpm, Netlify, Supabase) do not match, as the steps would fail or need local rewriting

Try asking

  • “Ship this change: add the changelog entry, run the tests, commit and push it to main”
  • “Publish the current main live and confirm the site works afterwards”
  • “Measure the size of my staged changes and the pending push before I commit”
  • “Update the changelog with screenshots for the balance tweak I just made”
Step-by-step guide: how to use Ship a ChangeInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 5 original files, the MIT licence and an attribution note.

    workflow-ship-change.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip workflow-ship-change.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip workflow-ship-change.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Read the project's AGENTS.md and any references file first, since the skill says project rules override it
  • Review the scripts before running them, especially verify-live.sh and push-main.sh, which fetch from and push to the remote
  • Keep an eye on the size the scripts report and answer the agent's prompt before any large upload

What's inside

  • scripts/commit-size.sh
  • scripts/push-main.sh
  • scripts/upload-size.sh
  • scripts/verify-live.sh
  • SKILL.md

Redistributed unmodified from MengTo/Skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.