القائمة
Run long or multi-checkpoint repository work through Hermes Kanban with autonomous OpenAI author/reviewer routing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | hermes-flow-v2 |
| description | Run long or multi-checkpoint repository work through Hermes Kanban with autonomous OpenAI author/reviewer routing. |
| version | 1.0.0 |
| platforms | ["linux"] |
| metadata | {"hermes":{"tags":["coding","kanban","review","codex"],"related_skills":[]}} |
Load this skill for repository work with more than one checkpoint/PR or an expected duration over 30 minutes. Do
not continue such work through a chain of chat --resume sessions.
preflight → author → commit → reviewer → CI/PR → merge → cleanup. Store artifacts under /home/uap/swarm-out/<mission>/ and attach their paths to task results./home/uap/swarm-bin/flow_contract.py delivery-route with the installed policy/signals and then
guard-repo for the exact repository, remote, branch, and disposable worktree. An activated profile must be schema
v3 with three to seven bounded correction retries after the initial candidate; migrate it only while its timer is
stopped. The canonical contract rejects any review cycle above eight.codex exec --sandbox read-only. Immediately before it starts, create
an attest-source artifact and include its printed marker once in the review prompt. Summarize each Codex JSONL
together with its matching local rollout and source artifact; runtime provider, model, sandbox, cwd and source SHA must match
the resolved route and role. For
same_provider_independent, the exact reviewer model must differ from the author model. The reviewer reads the real
diff, runs checks, and produces verification.json; it never edits, commits, pushes, or merges.summary.json and verification.json against the persisted canonical route decision, current HEAD and
green required CI. No manual model/review waiver exists.terminal-check.mission_adapter.py ingress/sync boundary and
preserve its mission_id/tenant. Never bypass its idempotency key. --allow-dispatch additionally requires the
configured profile, an explicit assignee and a non-scratch workspace.The full command reference and artifact schemas are in runbooks/hermes-flow-v2.md in
PavelLizunov/unified-agent-platform.
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).
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.
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.