メニュー
Commit a change and get it pushed. The git origin + write deploy key live ONLY on uap-ops-1 (100.82.241.121), NOT the workstation. Use whenever a change is ready to land.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run long or multi-checkpoint repository work through Hermes Kanban with autonomous OpenAI author/reviewer routing.
Take a routine on-demand k3s etcd snapshot and confirm it reached offsite R2. Non-destructive. Use for ad-hoc backups. RESTORE is NOT covered here (it is destructive + owner-gated).
Deploy a change to the cluster via Flux GitOps and VERIFY it actually reconciled. Use after editing anything under clusters/prod. A push alone is NOT a verified deploy.
Offload a token-HEAVY, quote-verifiable read (big log/doc/corpus) to the free local LLM so the big input never enters this paid context. Use when you are about to read a large file only to extract/locate/enumerate specific facts. NOT for judgment, synthesis, code edits, or small inputs.
Encrypt a Kubernetes Secret with SOPS for clusters/prod. MUST run on uap-home-1 (sops is absent on Windows; the age private key lives only there). Use when adding/rotating any secret.
Run the UAP validation gate (tests/verify-local.ps1) and interpret its result. Use before handing any change back, and before any commit/push. Knows the success tokens and which failures are EXPECTED on the Windows workstation.
| name | uap-commit-push |
| description | Commit a change and get it pushed. The git origin + write deploy key live ONLY on uap-ops-1 (100.82.241.121), NOT the workstation. Use whenever a change is ready to land. |
origin. git push there fails. Git operations happen FROM uap-ops-1 (100.82.241.121) via the repo-scoped read-WRITE SSH deploy key. gh is authed on ops-1 (account PavelLizunov). Identity is already set: UAP Agent <slovnmi@gmail.com>.master is protected by the protect-master ruleset: a direct git push origin master is REJECTED. Changes land via a PR that requires a green static-checks CI check (0 human approvals — the owner doesn't review). After merge, Flux reconciles master. See docs/next-steps.md, ADR-026.python tests/static/secret_scan.py . and, if you touched hermes/, python -m unittest discover -s hermes/tests -p 'test_*.py'). Do not proceed if it fails.git checkout -b <type/short-topic>
git commit -m "type(scope): summary" -m "Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>"
git push -u origin <type/short-topic> # the deploy key may push non-master branches
gh opens/merges the PR):
gh pr create --base master --head <type/short-topic> --title "type(scope): summary" --body "..."
gh pr merge --auto --squash <pr-number> # merges automatically once `static-checks` is green
static-checks is green. Then Flux reconciles master.git push origin master directly (blocked by the ruleset) or use --no-verify.protect-master ruleset to force a change in — fix the failing check instead.Authoritative reference: AGENTS.md -> Git Remote Readiness, STATUS.md, ADR-026, docs/next-steps.md.