Menú
Rules for PACMAN node agent PostgreSQL observation, lifecycle actions, and state reporting.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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.
PACMAN domain rules for cluster state transitions and operation history.
Rules for PACMAN control-plane quorum, leases, epochs, fencing, and split-brain prevention.
| name | node-agent-postgres |
| description | Rules for PACMAN node agent PostgreSQL observation, lifecycle actions, and state reporting. |
Use when changing pacmand node behavior, PostgreSQL probes, lifecycle actions,
or member reporting.
Primary locations:
internal/agent: node-side orchestration and reporting.internal/postgres: PostgreSQL commands, probes, WAL/LSN, recovery, standby.internal/peerapi: member-to-member API behavior.cmd/pacmand, internal/app/pacmand: process wiring.Rules: