← ClaudeAtlas

commit-push-prlisted

Commit, push, and open a PR. Use when the user wants to ship changes, create a pull request, or says things like 'commit and push', 'open a PR', 'ship it', 'send it', 'create a PR for this', or 'push this up'.
ClipboardHealth/groundcrew · ★ 40 · Code & Development · score 77
Install: claude install-skill ClipboardHealth/groundcrew
## Context - Current branch: !`git branch --show-current` - Git status: !`git status --short` - Commits ahead of default branch: !`git log --oneline origin/HEAD..HEAD 2>/dev/null || echo "(unknown)"` - Existing PR: !`gh pr view --json url --jq .url 2>/dev/null || echo "none"` - Diff summary: !`git diff HEAD --stat` - Full diff: !`git diff HEAD` ## Your task If `Commits ahead of default branch` is `(unknown)`, `origin/HEAD` couldn't be resolved — stop and tell the user to run `git remote set-head origin -a` (or otherwise set the default branch) before retrying, since the simplify step also depends on it. Otherwise, if `Git status`, `Commits ahead of default branch`, and `Existing PR` are all empty/none, stop and reply `nothing to ship.`. Otherwise: Before doing any step, output the full 7-step checklist below in your first response so it stays in recent context across sub-skill calls. Do not skip this — it's what keeps you from stopping after `simplify`. Use this PR body shape when creating or refreshing descriptions: ```md ## Summary Briefly explain the user intent from session history and the meaningful behavior/system change. If intent cannot be determined from the session or diff, ask the user before creating or refreshing the PR. Do not write a file-by-file changelog. ## Validation - List proof of validation: commands, screenshots, telemetry, Loom, or `Not run: <reason>`. ## Notes Optional: ticket links, rollout plan, residual risk, or areas for reviewers to fo