testing-governance-gates

Tests CI governance gates and automerge advisory versus required check behavior.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill testing-governance-gates-amitabhainarunachala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-governance-gates
Source: https://github.com/AmitabhainArunachala/dharma_swarmv.01/tree/main/.agents/skills/testing-governance-gates
Command: npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill testing-governance-gates-amitabhainarunachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that advisory governance checks warn without blocking merges while required CI checks always block is error-prone when done ad hoc, and a broken filter can silently pass everything. ## Core Features & Use Cases - Advisory-gate test: Runs scripts/runtime/ci_truth.py against a synthetic rollup JSON where governance checks fail, expecting verdict DEGRADED with empty merge_blockers. - Required-check control test: Flips a required check (DocOps integrity gate) to FAILURE and confirms verdict FAIL with a docops_integrity merge blocker, proving the gate still bites. - Automerge filter test: Extracts the jq filter live from .github/workflows/automerge.yml and runs it against synthetic statusCheckRollup fixtures to confirm advisory failures are ignored while real test failures block. - Use Case: After editing CI workflows or the CI_TRUTH_CONTRACT.json, run all three tests to prove the advisory/required split still holds before merging. ## Quick Start Run the governance gate tests against this checkout and report the verdict for the advisory, required-control, and automerge filter cases.

Frequently Asked Questions about testing-governance-gates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test CI governance gates locally without GitHub Actions?▼

Run scripts/runtime/ci_truth.py with the --rollup-json flag pointing at a synthetic check rollup JSON file. This produces a verdict and merge_blockers list locally, requiring no GITHUB_TOKEN or network access.

How do I verify automerge ignores advisory check failures?▼

Extract the jq filter directly from .github/workflows/automerge.yml in the checkout under test, then run it against synthetic statusCheckRollup fixtures. Failed governance checks alone should yield not_green=0, while a failed required test yields not_green=1.

What is the difference between advisory and required CI checks?▼

Required checks are listed in docs/governance/CI_TRUTH_CONTRACT.json and their failure produces verdict FAIL with entries in merge_blockers. Advisory checks like Coherence Delta and ACTIVE_TRACK produce verdict DEGRADED with empty merge_blockers, acting as warnings only.

Why must the required-check control test always run with the advisory test?▼

A filter that ignores everything would also pass the advisory-only test, hiding a dead gate. The control test sets a required check to FAILURE and confirms verdict FAIL, proving the gate still blocks real failures.

Why do synthetic rollups produce missing advisory warnings?▼

Small synthetic rollups omit many advisory entries listed in the CI truth contract, so the tool warns about them. This is expected and harmless as long as merge_blockers and the targeted advisory statuses match expectations.