← ClaudeAtlas

shiplisted

Land a change safely: sync base, verify, review the diff, then commit/push/PR. Use when finishing a piece of work. Triggers: "ship it", "land this", "open a PR", "create a PR", "commit and push", "ready to merge".
gnibu/bento · ★ 0 · Code & Development · score 68
Install: claude install-skill gnibu/bento
# Ship Take work from "done on my machine" to a reviewable PR, git/file-only so it runs the same under any agent. Consolidates commit + PR into one flow. Nothing lands without passing the repo's own checks and your own diff review. ## Steps (paste as todos) 1. **Sync the base branch.** Identify the base (the repo's default/integration branch, not `main` if the repo integrates elsewhere). Fetch and merge/rebase it into your branch; resolve conflicts before anything else. 2. **Verify — the repo's own checks.** Run whatever exists: tests, lint, type-check, build (`just check`, `npm test`, `pytest`, etc. — discover from the repo, don't assume). Fix failures. Green is the gate; "it compiles" is not. 3. **Review your own diff.** Read `git diff <base>...HEAD` end to end. Check: scope matches the task (no stray files, no debug code, no secrets), and every change is intended. 4. **Version + changelog, if the repo has them.** Bump the version and add a changelog entry matching the repo's convention. Skip cleanly if neither exists. 5. **Commit** in conventional style, one logical change per commit. If a commit hook reformats files, re-stage and retry. 6. **Push and open the PR** against the base branch, with a title/body derived from the actual diff (not the branch name). Create a PR only when the user asked — a commit is not a PR request. 7. **Prove it.** Report the PR URL and that checks passed. If CI runs, note its status. ## Guardrails - Pushing, merg