القائمة
PACMAN distributed-systems testing rules for Jepsen-style failures and invariants.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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 | jepsen-testing |
| description | PACMAN distributed-systems testing rules for Jepsen-style failures and invariants. |
Use for changes in jepsen/**, tools/jepsenctl/**, HA safety, or failure
injection behavior.
Primary locations:
jepsen/README.md, jepsen/TODO.md, jepsen/UNSUPPORTED.md.tools/jepsenctl/cmd: runner, harness, checkers, target/case registry.mk/jepsen.mk: local and CI entrypoints.Rules:
jepsen/UNSUPPORTED.md.go test -count=1 ./tools/jepsenctl/cmd, then the
smallest make jepsen-docker-case-* target needed.