kacerrandClaude Opus 5.5
5fd998c5f9
Phase 1-3 runbooks and design notes, version pins, config templates, project-history conventions, cluster-inspector read-only credentials setup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
---
|
|
description: Commit current changes and push to the remote
|
|
---
|
|
|
|
Commit the current working-tree changes and push them.
|
|
|
|
1. Run `git status` and `git diff` to see what will be committed.
|
|
2. Check the staged content for secrets: Proxmox token secrets, kubeconfig contents, anything
|
|
`.gitignore` would have caught by name but that was pasted into a doc. Stop and report if found.
|
|
3. Check the current branch (`git branch --show-current`). Docs, configs and history files may go
|
|
straight to `main`. If on `main` and the diff contains phase-3 Go code or something the user
|
|
called a feature, stop and tell the user to branch first (CLAUDE.md "Git").
|
|
4. If an approved plan is in progress, make sure its execution log in `docs/plans-executions/` is
|
|
updated and its checklist ticked for the steps included in this commit.
|
|
5. Stage the changed files (`git add -A` is fine here).
|
|
6. Commit with a short message inferred from the diff, ending with the `Co-Authored-By:` trailer
|
|
for Claude. Pass the message via a HEREDOC.
|
|
7. Push with `git push`; if the branch has no upstream, `git push -u origin HEAD`.
|
|
8. If the branch isn't `main`, remind the user to open an MR with `tea pr create` rather than
|
|
opening one automatically.
|
|
9. Report the commit hash and push result.
|
|
|
|
If there are no changes, stop and say so; do not create an empty commit.
|