ship
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add whyashthakker/estack --skill shipCompatible with
Supported agents
Finish and ship a change safely.
Checks what changed, runs the project's own typecheck, lint, and tests, stages only the files this task touched, writes a short commit message, updates the changelog only for real product changes, and pushes after the user agrees.
Use when the user says "ship it", "push", "commit and push", "deploy", "we're done", or asks to update release notes.
| name | ship |
| description | Finish and ship a change safely. Checks what changed, runs the project's own typecheck, lint, and tests, stages only the files this task touched, writes a short commit message, updates the changelog only for real product changes, and pushes after the user agrees. Use when the user says "ship it", "push", "commit and push", "deploy", "we're done", or asks to update release notes. |
Goal: the change lands clean, small, and easy to undo. Nothing extra goes with it.
Run git status, git diff --stat, and git log origin/<branch>..HEAD. Sort the files into:
Never stage .env*, secrets, large binaries, or build output.
Find the project's own commands (package.json scripts, Makefile, justfile, CI config) and run the fast ones: typecheck, lint, unit tests for the touched area. Ask before a slow full build.
Confirm that each check really ran: read the output, not only the exit code. A command that was not found, or a test runner that found zero tests, is not a pass. If a check fails, fix it or stop and report. Do not ship red.
Update the changelog or release notes only when a user of the product would notice the change: a new feature, a pricing or account change, a redesign, a fixed bug they reported. Content (blog posts, docs copy), refactors, and internal tools do not go in a public changelog. When in doubt, leave it out.
git add path/a path/b. Not git add -A.git log).Ask before you push unless the user already said to. Before you push to the default branch, check whether the push starts a deploy or kills a running job (CI config, deploy hooks). If the push is rejected, pull with rebase, run the checks again, then push. Never force-push a shared branch.
Commit hash, what shipped, what you did not stage and why, and the checks that ran.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionshipExecute the skills CLI command in your project's root directory to begin installation:
epx add whyashthakker/estack --skill shipFetches ship from whyashthakker/estack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/ship
Restart Cursor to activate ship. Access via /shipin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Registry listing for ship matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: ship is the kind of skill you can hand to a new teammate without a long onboarding doc.
ship reduced setup friction for our internal harness; good balance of opinion and flexibility.
ship reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in ship — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend ship for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend ship for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in ship — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in ship — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend ship for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 65