skill
Consensus Code Merge Guard
Applies persona-weighted governance to merge decisions using test, security, and reliability signals.
Why merge governance matters
Passing CI is necessary but not sufficient. High-impact code changes still need structured arbitration across risk perspectives.
Inputs considered
- PR/change summary
- test status and required checks
- security markers in diff summary
- project constraints (e.g., block on security flags)
Outputs
MERGE | BLOCK | REVISE plus required follow-up actions and board artifact references.
Why engineering teams use it
- prevents silent risk acceptance
- standardizes review decisions across repositories
- creates traceable merge governance history
SKILL.md perspective
Designed for deterministic policy behavior with strong automation compatibility.
AI-SELF-IMPROVEMENT perspective
Release decisions become measurable governance signals, enabling continuous calibration of evaluator quality.
Source Documentation
For exact source documentation, open the raw markdown views below.