Push

You are committing and pushing the current work in one shot: generate a commit message (the same way /commit does), then actually run stage → commit → push. Unlike /commit, this skill does execute git.

This skill stops at the push. Whatever branch you're on, it stays that branch — no new branch, no PR, no merge. If the user wants the work landed in main, that's /merge.

Custom instructions: If the user included extra instructions when invoking this skill, treat them as overriding or extending the guidance below (e.g. a message they dictate, or a specific remote).

1. Check you can ship

git status --porcelain
BRANCH="$(git branch --show-current)"
echo "current=$BRANCH"

• If git status --porcelain is empty, stop and tell the user — don't create an empty commit.
• If BRANCH is empty you're in detached HEAD. Stop and report; don't guess a branch.

Scan the file list before staging. This skill stages everything, so glance at what "everything" is. Speed is the point — say nothing and keep going unless something genuinely doesn't belong:

• OS / editor junk — .DS_Store, Thumbs.db, .idea/, *.swp. Don't commit these. Add them to .gitignore instead, mention it in one line, and continue.
• Possible secrets — .env, .env.local, *.pem, *.key, credentials*, *.p12. Stop and ask. Never commit one on your own initiative.
• Clearly unrelated work — untracked scratch files, or edits in a part of the repo the current work never touched. Name them in one line and ask whether to include them, since the commit message won't describe them.

Anything else, just stage it. Don't narrate a clean file list, and don't turn this into an approval step — /push is meant to be one shot.

2. Generate the commit message

Read skills/commit/SKILL.md and follow its steps 1–3 — figuring out what changed, checking .docs/commit-convention.md (detecting or asking and persisting it if missing), and writing the message — exactly as /commit would. Stop before its step 4 (Output): that step is /commit-specific ("print it, don't touch git") and doesn't apply here. Keep the message you produced; use it for staging and committing below.

The convention check is the one narrow exception to "push without asking" in this skill — same category as the secrets check in Step 1. It only asks the user directly when .docs/commit-convention.md doesn't exist yet and recent history is genuinely ambiguous; once answered it's persisted to that file and never asks again.

3. Push without asking

Running this skill is the confirmation. Do not ask the user to approve the message — invoking /push already means "commit this and push it". If they only wanted the message, they would have run /commit. Proceed straight to the remaining steps. (You may state the message as you go, but don't pause for approval.)

4. Obey the project's own pre-ship rules

If CLAUDE.md (or equivalent workspace rules) defines steps that must happen before shipping — a validation script, a version bump, a changelog entry — do them now, before anything is committed. If one fails, stop and report; don't ship a knowingly broken commit. If the project defines no such steps, skip straight to the next section.

5. Run it

Write the full message to a temp file so multi-line bodies survive shelling out:

MSG_FILE="$(mktemp)"
cat > "$MSG_FILE" <<'EOF'
<the generated commit message goes here>
EOF

git add -A && \
git commit -F "$MSG_FILE" && \
git push -u origin HEAD && \
rm -f "$MSG_FILE"

Notes:

• If the push is rejected as non-fast-forward (the remote moved), run git pull --rebase once and push again. If the rebase hits conflicts, stop and report them — don't resolve them silently and never force-push.
• If the push is rejected because the branch is protected, stop and tell the user the branch requires a PR, so /merge from a feature branch is the way in. Don't create a branch behind their back.
• If any other step fails, stop and report the exact error. Don't retry blindly.

6. Report

One or two lines: the commit title and the branch it was pushed to. Say plainly that no PR was opened — if they want it merged into main, /merge is next. Or report exactly where it stopped and why.