guard

Runs mechanical integrity checks on pipeline artifacts and installs them as a CI gate.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/AiFirstDevelopment/quorum --skill guard-aifirstdevelopment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/AiFirstDevelopment/quorum/tree/main/plugins/quorum/skills/guard
Command: npx skills add https://github.com/AiFirstDevelopment/quorum --skill guard-aifirstdevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted delivery pipelines rely on prompt-level rules that an agent can talk itself out of. Guard enforces the rules a machine can settle — unchanged requirements, unweakened tests, append-only reviews, self-consistent verdicts, and real evidence — so violations are reported mechanically instead of being adjudicated away. ## Core Features & Use Cases - Mechanical rule checks: Verifies requirements immutability, test integrity (no deletions, skips, or only markers), append-only review records, verdict consistency, criterion coverage, evidence validity, and branch placement. - CI gate installation: Vendors the checker to .quorum/guard.py and writes a GitHub Actions workflow (with GitLab guidance on other hosts), plus a --check-gate mode that reports whether branch protection is actually live. - Self-testing checker: Ships a self-test suite that builds throwaway repositories, breaks each rule deliberately, and asserts the rule fires. - Use Case: Before merging an AI-produced pull request, run the guard to confirm no acceptance criterion was silently omitted from the verdict and no test was weakened, then make it a required status check so violations block merges. ## Quick Start Run the guard checks on my current work item and report any violations found.

Frequently Asked Questions about guard

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

FAQPage Schema
How do I run mechanical checks on an AI-generated pull request?▼

Run guard.py against the work item's branch to check requirements immutability, test integrity, append-only reviews, verdict consistency, and evidence validity. It exits 0 when clean, 1 on violations, and 2 when it cannot run.

How do I add a CI gate that blocks merges on rule violations?▼

Run guard.py with --install-ci to vendor the checker to .quorum/guard.py and write a GitHub Actions workflow. Then make the check a required status check in branch protection settings, which only a repo admin can do.

Does the CI gate installation work on GitLab or other hosts?▼

The checker is host-agnostic and always vendored, but the workflow file is only written on GitHub remotes. On GitLab it prints a ready-to-paste .gitlab-ci.yml job, and you make it required in merge request settings manually.

Why does the guard report a vendored violation after a plugin update?▼

The vendored copy in .quorum/guard.py is frozen at the rules it was written with. When it stops matching the plugin's checker, a vendored violation fires so you re-run --install-ci and enforce the current rule set.

What happens when the gate status cannot be determined?▼

When gh is missing or admin rights are unavailable, --check-gate reports that it cannot tell rather than rounding up to a pass. The pipeline records this answer in the pull request body without treating it as a defect.