compliance-verifier

Verifies compliance evidence on pull requests and posts an advisory compliance-check status.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill compliance-verifier-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compliance-verifier
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/profiles/soc2-baseline/skills/compliance-verifier
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill compliance-verifier-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Compliance evidence drafted by AI agents can contain dangling evidence pointers, pre-signed attestations, or fabricated results that slip into the ledger. This Skill adds a second review pass on compliance-evidence pull requests so the human executive signs off on verified, complete evidence instead of unvetted drafts. ## Core Features & Use Cases - Evidence Verification: Confirms that evidence pointers in compliance/evidence-ledger.yml resolve to real files and that the evidence doc contains substantive assessment content rather than empty templates. - Anti-Laundering Checks: Detects pre-signing attempts where a draft claims source: human-attested without a human edit, and flags too-good-to-be-true results with zero findings for extra executive scrutiny. - Advisory Status Reporting: Posts a compliance-check status (success/failure) with findings and guidance on what the executive should examine before signing, without blocking the merge. - Use Case: When a PR appends a new SOC 2 access-review artifact to the evidence ledger, this Skill checks that the collaborator table is real, the interval matches the issue, and findings are surfaced, then comments with anything the executive must verify before approval. ## Quick Start When a pull request touching compliance/evidence-ledger.yml opens, review the drafter's evidence for missing or wrong content and post an advisory compliance-check status with your findings.

Frequently Asked Questions about compliance-verifier

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

FAQPage Schema
How do I verify compliance evidence on a GitHub pull request?▼

Fetch the PR diff with gh pr diff, confirm each artifact's evidence path exists in the PR tree, and check the evidence doc contains real assessment content per control type. Then post a compliance-check status summarizing findings for the human approver.

What does the compliance-check status on a PR mean?▼

It is an advisory status posted by an automated verifier indicating whether the drafted compliance evidence passed checks for pointer resolution, substance, and signing integrity. It informs the executive's review but does not block merging; the human-approval gate remains the required control.

Can this verifier approve or merge compliance pull requests?▼

No. It holds only code:review (statuses:write) scope and posts an advisory status. It never approves, signs, or closes anything; the executive performs signing and the generic reviewer plus human-approval gate control the merge.

Why does a clean compliance result get flagged for extra attention?▼

A substantive control like access-review or vendor-reassessment returning zero findings and zero open items is statistically suspicious. The verifier flags it so the executive confirms the clean result rather than letting a potentially superficial review sail through.

What are the limitations of an AI compliance verifier?▼

It may share the same model lineage as the drafting agent, so it can share blind spots and is a floor-raiser rather than an independent assurance. Where the substrate offers a different model or provider for verification, that should be used to reduce correlated errors.