Menu
PACMAN domain rules for cluster state transitions and operation history.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Require a concrete change explanation and explicit user approval before modifying a repository, then implement and verify the approved scope. Use whenever Codex is asked to create, edit, delete, generate, format, refactor, fix, upgrade, or otherwise mutate repository files, dependencies, configuration, tests, documentation, build artifacts, or version-control state.
Repository layout for the pacman Go PostgreSQL HA cluster manager.
Use when inspecting GitHub Actions, CI failures, failed Go tests, workflow logs, or build/lint/test errors. Avoid reading full logs; summarize failed jobs and inspect only relevant snippets.
Maintain PACMAN-native and Patroni-compatible API contracts.
Rules for PACMAN control-plane quorum, leases, epochs, fencing, and split-brain prevention.
Minimal Go build, test, debug, and lint workflow for pacman.
| name | cluster-state-machine |
| description | PACMAN domain rules for cluster state transitions and operation history. |
Use for failover, switchover, rejoin, maintenance, roles, epochs, and history.
Primary locations:
internal/cluster: state model, roles, maintenance, operations, specs.internal/controlplane: transition planning/execution and operation history.docs/ARCHITECTURE.md, docs/TODO.md: architecture and product roadmap.Rules: