kacerrandClaude Opus 5.5
2be69b9aac
- /ship now commits and pushes with a branch guard and no longer tags; /release tags vMAJOR.MINOR.PATCH and confirms before pushing - operator-reviewer and go-operator-reviewer agents from egress-proxies-operator - committed permission allowlist; settings.local.json ignored Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
description
| description |
|---|
| Commit current changes and push to the remote |
Commit the current working-tree changes and push them.
- Run
git statusandgit diffto see what will be committed. - Check the current branch (
git branch --show-current). If it'smainand the change looks feature-sized (not one of CLAUDE.md's "commit straight to main" exceptions: small fixes, typos/formatting, or the user explicitly saidmain), stop and tell the user to branch first — don't push a feature tomain. - Stage the changed files (
git add -Ais fine here). - Create a commit with a short message describing the changes (infer it from the
diff), including a
Co-Authored-By:trailer for Claude. Pass the message via a HEREDOC. - Push with
git push. If the current branch has no upstream, usegit push -u origin HEAD. - If the branch isn't
main, remind the user to open an MR withtea pr create(see CLAUDE.md's Branching & Merge Requests section) rather than opening one automatically. - Report the commit hash and push result.
If there are no changes, stop and say so — do not create an empty commit.