Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Persona-weighted merge governance for AI-assisted engineering. Evaluates PR risk (tests, security markers, reliability signals), returns MERGE/BLOCK/REVISE d...
Persona-weighted merge governance for AI-assisted engineering. Evaluates PR risk (tests, security markers, reliability signals), returns MERGE/BLOCK/REVISE d...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
consensus-code-merge-guard turns code merge approval into a governed, auditable decision.
consumes PR/change summary input runs persona-weighted vote arbitration enforces hard constraints (e.g., tests/security flags) maps to engineering decision states: MERGE | BLOCK | REVISE writes decision and updated persona artifacts to board state
CI passing does not guarantee risk-aware merge quality. Consensus review reduces silent failure propagation into production.
Uses the same consensus substrate as other guards, enabling cross-domain governance with comparable metrics.
autonomous or semi-autonomous merge pipelines high-risk repos needing policy checks repeatable release governance with artifact history
runtime binaries: node, tsx network calls: none in the guard decision path itself filesystem writes: board/state artifacts under the configured consensus state path
consensus-guard-core is the first-party consensus package used in guard execution versions are semver-pinned in package.json for reproducible installs this skill does not request host-wide privileges and does not mutate other skills
npm i consensus-code-merge-guard
node --import tsx run.js --input ./examples/input.json
This skill is wired to the consensus-interact contract boundary (via shared consensus-guard-core wrappers where applicable): readBoardPolicy getLatestPersonaSet / getPersonaSet writeArtifact / writeDecision idempotent decision lookup This keeps board orchestration standardized across skills.
This skill exposes a canonical entrypoint: invoke(input, opts?) -> Promise<OutputJson | ErrorJson> invoke() starts the guard flow and executes deterministic policy evaluation with board operations via shared guard-core wrappers.
Guards support two modes: mode="external_agent": caller supplies external_votes[] from agents/humans/models for deterministic aggregation. mode="persona": requires an existing persona_set_id; guard will not generate persona sets internally.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.