Workflow Ship Change
Ship every change the way the user requires, with the guardrails. Take screenshots of the start, the key moment and the result; give the change its own changelog version with pictures; verify with tests; commit only your own files; merge with the latest main and push as a fast-forward; publish that exact main live; confirm each step; and report measured sizes, asking before any upload over 50 MB. Use at the end of every change (feature, fix, tweak, art, balance, polish) and whenever the user says "ship it", "commit", "push", "merge", "publish", "deploy", "go live" or "update the changelog". Pr
Install
npx skills add MengTo/Skills --skill workflow-ship-changegit clone --depth 1 https://github.com/MengTo/Skills.git /tmp/Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Skills/agent-skills/workflow/workflow-ship-change ~/.claude/skills/workflow-ship-changePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Workflow: ship a change A change is **done** only when all of these are true, and the report shows each one: 1. **Screenshots** of the real rendered game: the start state, the key moment and the result. They're shown inline in the report. 2. **Its own changelog version**, with its pictures on the in-game changelog page. 3. **Verified**: - your own tests; - the tests of commits you merged in; - the asset checks; - the full suite, run on the pushed commit. 4. **Committed**: one cohesive commit, with only your own files staged. 5. **Pushed** to `main` as a fast-forward, and confirmed on GitHub. 6. **Live**: the build of that exact `main` is published, and confirmed working on the real domain. 7. **Measured**: the sizes of the commit, the push, any upload and the publish, all measured, never estimated. Pushing and publishing are standing authorizations for the project's own repository and live site. So don't ask before them, **except** where a guardrail below says stop. Read the project's `AGENTS.md` before starting, and this skill's `references/<project>.md` if there is one. Project rules change often, and wherever they differ from this skill, they win. ## Guardrails: stop and ask the user - **Any upload over 50 MB.** That covers a git push, a Netlify deploy, a media release, and files sent to any outside service. - Measure first (`upload-size.sh`, or the pack size `push-main.sh` prints), and state the size when asking.
Details
- Skill name
workflow-ship-change- Repository
- MengTo/Skills
- Path
agent-skills/workflow/workflow-ship-change/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
FAQ
What does the Workflow Ship Change skill do?
Ship every change the way the user requires, with the guardrails. Take screenshots of the start, the key moment and the result; give the change its own changelog version with pictures; verify with tests; commit only your own files; merge with the latest main and push as a fast-forward; publish that exact main live; confirm each step; and report measured sizes, asking before any upload over 50 MB. Use at the end of every change (feature, fix, tweak, art, balance, polish) and whenever the user says "ship it", "commit", "push", "merge", "publish", "deploy", "go live" or "update the changelog". Pr
How do I install the Workflow Ship Change skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add MengTo/Skills --skill workflow-ship-change. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Workflow Ship Change popular?
It lives in MengTo/Skills, which has 7,717 GitHub stars and 885 forks.
Related skills
3d Cloth Material
7.7kMengTo/Skills
Build convincing woven cloth in Three.js, with a thread-level weave normal map, sheen and anisotropic highlights, folds that never stretch the texture, hems with thickness, stitches, seams, frayed edges, fold occlusion, dye and wear variation, and light passing through thin fabric. Use for linen, silk, wool, canvas, curtains, banners, cloaks, tablecloths, tapestries or any 3D drape that currently looks like a plastic sheet, a stretched texture, or a flat coloured plane.
3d Falling Leaves
7.7kMengTo/Skills
Build recognizable falling leaves in world space using instanced geometry, independent tumble, coupled sideways drift, shared wind, scene occlusion, and camera-aware recycling. Use for 3D autumn leaves or drifting foliage in Three.js and similar scenes; use falling-leaves for a 2D canvas overlay.
3d Four Seasons
7.7kMengTo/Skills
Add coordinated spring, summer, fall, and winter states to a 3D scene, blending foliage, sunlight, sky, ground materials, snow, and particles without rebuilding the world. Use for seasonal controls, architectural walkthroughs, and outdoor scenes with four-season transitions.
Workflow Threads Manager
7.7kMengTo/Skills
Oversee the other Claude threads (sessions) working on the same project. Check what each is doing, confirm finished work is merged to main, has its changelog entry with screenshots, and is live, archive threads that are truly done, and restart or flag threads that were cut off. Use when the user says "check threads", "check new changes", "are the threads merged and pushed", "archive the done threads", or asks what the other sessions are up to. Project specifics (changelog format, live site, capture folders) go in an optional local references/<project>.md next to this skill.
Workflow Score to Target
7.7kMengTo/Skills
Score work out of 10 against a clear rubric, then improve it round by round until every item reaches the target score the user named (for example "get it to 8 out of 10", "bring everything under 6 up to 6+"). Covers anchored rubrics, measurable criteria, independent or blind judging, before/after scorecards, and honest reporting of anything still short. Use whenever the user asks to score, rate, grade or judge something out of 10, names a target score, or asks "what would make this a 9?".
Cua Driver
4.3kdavidondrej/skills
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.