contract-enforcement-auditor

Audits codebases for contract violations and enforcement gaps in ESLint rules, CI gates, and runtime guards.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/bmsull560/Fabric_4L --skill contract-enforcement-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-enforcement-auditor
Source: https://github.com/bmsull560/Fabric_4L/tree/main/.windsurf/skills/contract-enforcement-auditor
Command: npx skills add https://github.com/bmsull560/Fabric_4L --skill contract-enforcement-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans codebases to identify violations of canonical contracts and enforcement gaps between documented contracts and runtime behavior, enabling proactive compliance.

Core Features & Use Cases

  • Detects contract violations across contract.md and highlights enforcement gaps in ESLint rules, CI gates, and runtime guards.
  • Generates actionable remediation guidance and supports weekly or release-scoped audits.
  • Use Case: Before release, audit for enforcement gaps to ensure code aligns with documented contracts.

Quick Start

Run the contract enforcement audit against your repository to reveal enforcement gaps and ensure runtime and CI alignment.

Frequently Asked Questions about contract-enforcement-auditor

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

FAQPage Schema
How do I audit my codebase for contract enforcement gaps before a release?

An enforcement gap audit identifies violations of canonical contracts by comparing documented contract.md rules against actual ESLint configurations, CI gates, and runtime guards to pinpoint where code behavior diverges from specifications.

What do I need to run a contract enforcement assessment on my repositories?

A contract enforcement audit detects canonical contract violations and generates actionable remediation guidance for enforcement gaps found across ESLint rules, CI gates, and runtime guards, supporting both weekly and release-scoped compliance checks.

How do I check if my ESLint rules and CI gates align with documented contracts?

To start auditing contract enforcement, run the audit against your repository to reveal enforcement gaps, verify runtime and CI alignment with documented contracts, and generate actionable remediation guidance for any identified violations.

When should I not use an automated contract enforcement audit?

Enforcement gap audits are best suited for enterprise repositories containing contract.md, ESLint rules, CI gates, and runtime guards, and may not yield useful results for smaller projects lacking these canonical contract documentation files.