Consensus Code Merge Guard for Openclaw

A persona-weighted governance tool for AI-assisted engineering that evaluates PR risks and automates merge decisions.

kaicianflone
v1.1.15
Mar 3, 2026
0
1.1k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install consensus-code-merge-guard

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install consensus-code-merge-guard using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Consensus Code Merge Guard?

Consensus Code Merge Guard transforms the standard code approval process into a governed, auditable decision-making framework. By moving beyond simple pass/fail CI checks, this tool evaluates complex pull request risks through persona-weighted arbitration, ensuring that reliability signals and security markers are thoroughly weighed before a merge occurs.

Integrating seamlessly into the Openclaw Skills ecosystem, it provides engineering teams with a structured way to handle autonomous or semi-autonomous code changes. It reduces the likelihood of silent failure propagation by enforcing hard constraints and recording every decision as a board-native audit artifact, ensuring transparency across the entire development lifecycle.

Consensus Code Merge Guard Use Cases

  • Managing autonomous or semi-autonomous merge pipelines that require deterministic governance.
  • Safeguarding high-risk repositories that demand strict policy checks and security enforcement.
  • establishing repeatable release governance with a comprehensive history of decision artifacts.

How Consensus Code Merge Guard Works

  1. The skill ingests a pull request or change summary along with necessary metadata.
  2. It initiates a persona-weighted vote arbitration process to evaluate the technical risk of the proposed changes.
  3. Hard constraints, such as security flags and test coverage requirements, are strictly enforced against the policy.
  4. The system determines a final engineering state: MERGE, BLOCK, or REVISE.
  5. Decision artifacts and updated persona data are written to the configured consensus state path for permanent record-keeping.

Consensus Code Merge Guard Setup

Install the package using npm:

npm i consensus-code-merge-guard

Set up the necessary environment variables to define your state management paths:

export CONSENSUS_STATE_FILE="path/to/state.json"
export CONSENSUS_STATE_ROOT="path/to/root/"

Execute the guard using node and tsx:

node --import tsx run.js --input ./examples/input.json

Consensus Code Merge Guard Data Schema & Taxonomy

This skill utilizes a structured data approach to ensure all decisions are reproducible and transparent within Openclaw Skills environments.

Element Description
CONSENSUS_STATE_FILE The primary JSON file tracking the current state of governance decisions.
CONSENSUS_STATE_ROOT The directory where board-native audit artifacts and persona sets are stored.
Decision Output A structured JSON response containing the final MERGE, BLOCK, or REVISE status.
Board Artifacts Metadata describing the weights, votes, and constraints used in the decision process.

Consensus Code Merge Guard Advanced Features

  • Dual operational modes: external_agent mode for manual/agentic vote aggregation and persona mode for fixed governance sets.
  • Integration with the consensus-interact contract boundary for standardized board operations.
  • Idempotent decision lookup capabilities to ensure stability across complex Openclaw Skills workflows.
  • Deterministic policy evaluation through the first-party consensus-guard-core substrate.

SKILL.md


Loading

Related Openclaw Skills

Featured*