enforce

Automate security enforcement across CI pipelines and repository governance.

3|3|Updated Jan 4, 2026

Search Tags:#security #provenance #pre-commit #policy-as-code #slsa #branch-protection #enforce

Ready to run

npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill enforce-adaptive-enforcement-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enforce
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/enforce/skills/enforce
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill enforce-adaptive-enforcement-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Automates security enforcement to ensure policies are mandatory and auditable.

Core Features & Use Cases

Branch protection that requires reviews and status checks, plus commit signatures to prevent unauthorized merges.
Pre-commit hooks and policy-as-code for deterministic enforcement in CI/CD and runtime.
SLSA provenance generation and audit-ready workflows for SOC 2, ISO 27001, and PCI-DSS alignment.

Quick Start

Enable enforcement controls in your repository by enabling branch protection, status checks, and pre-commit hooks, then layer in policy-as-code and SLSA provenance for end-to-end security.

Frequently Asked Questions about enforce

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

FAQPage Schema

How do I automate branch protection and pre-commit hooks for CI/CD pipelines?▼

Automate branch protection and pre-commit hooks by configuring policies that require reviews, status checks, and commit signatures. This blocks unauthorized merges and enforces security deterministically in CI/CD pipelines before deployment.

What is policy-as-code and how does it help with SOC 2 and ISO 27001 compliance?▼

Policy-as-code enforces security rules deterministically in code rather than manually. It generates audit-ready workflows and SLSA provenance, aligning development processes with SOC 2, ISO 27001, and PCI-DSS compliance requirements.

How do I generate SLSA provenance and prevent non-compliant changes from deploying?▼

Generate SLSA provenance and block non-compliant changes by layering policy-as-code and pre-commit hooks into your repository governance. This creates mandatory, auditable security enforcement across development workflows and CI pipelines.

Does the enforce Skill work with GitHub repositories and what are the prerequisites?▼

The enforce Skill works with GitHub repositories and requires the gh CLI tool as a dependency. It uses scripts to enable branch protection, status checks, and pre-commit hooks for automated security enforcement.

Can I use policy-as-code to make commit signatures and status checks mandatory across my repository?▼

Yes, policy-as-code makes commit signatures and status checks mandatory by automating their enforcement. This prevents unauthorized merges and ensures all changes satisfy branch protection requirements before integration.

What are the limitations of automating security enforcement with pre-commit hooks?▼

Automating security enforcement with pre-commit hooks requires proper local configuration and the gh CLI dependency. It enforces policies deterministically but developers must have the hooks installed locally to block non-compliant changes before pushing.