compliance-guard

Validate engineering artifacts against a YAML rules catalog with evidence-backed verdicts.

Updated May 9, 2026

Search Tags:#API contracts #policy enforcement #architecture governance #ADR review #compliance validation #rule catalog #waiver traceability

Ready to run

npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill compliance-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compliance-guard
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/compliance-guard
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill compliance-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compliance-guard helps you determine whether specs, APIs, data models, architectures, ADRs, and generated artifacts meet an explicit ruleset, producing auditable verdicts with evidence and traceability.

Core Features & Use Cases

Rule-catalog compliance checks: Evaluate each provided rule and classify outcomes as pass, pass with warnings, fail, or not verifiable.
Blocking vs non-blocking enforcement: Treat constraints as blocking, conventions as warnings by default, and policies as fail unless an appropriate waiver reference is provided.
Evidence-backed reporting: Include rule-level evidence (artifact sections/patterns) and generate a structured compliance report suitable for governance and approval workflows.

Quick Start

Use compliance-guard to validate your artifact against a YAML rule catalog you provide, and request a structured compliance report including blocking failures, warnings, and any not-verifiable items.

Frequently Asked Questions about compliance-guard

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

FAQPage Schema

How do I validate API contracts against architecture governance rules?▼

You validate API contracts against architecture governance rules by evaluating artifacts against a provided rules catalog to produce rule-level compliance verdicts with evidence. The process classifies constraints, conventions, and policies, aggregating results into a traceable compliance report.

What is policy enforcement for engineering artifacts?▼

Policy enforcement for engineering artifacts is the process of checking specs, data models, and ADRs against an explicit ruleset. It classifies constraints as blocking, conventions as warnings, and policies as fails unless a valid waiver reference is provided.

How do I generate an auditable compliance report for ADR review?▼

You generate an auditable compliance report for ADR review by validating the architecture decision record against a YAML rule catalog. The output includes rule-level evidence, blocking failures, warnings, and any not-verifiable items suitable for governance approval workflows.

Can I use a custom rule catalog for compliance validation?▼

Yes, you can use a custom rule catalog for compliance validation by providing your own YAML ruleset. The validation process evaluates each provided rule without inventing new ones, ensuring all checks map directly to your defined constraints, conventions, and policies.

How does waiver traceability work during governance gates?▼

Waiver traceability during governance gates works by allowing policies to pass with a fail verdict unless an appropriate waiver reference is provided. This ensures exceptions to blocking constraints are explicitly documented and auditable within the final compliance report.