compliance

Generate OpenAPI specs, contract tests, and missing unit tests to validate code compliance.

2|Updated Jan 30, 2026

Search Tags:#code quality #automation #testing #api #validation #compliance

Ready to run

npx skills add https://github.com/amdmax/claude_marketplace --skill compliance-amdmax

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the validation of code against business requirements, API specifications, and test coverage standards, preventing non-compliant code from entering production.

Core Features & Use Cases

API Contract Testing: Generates and validates OpenAPI specs and contract tests.
Test Coverage Analysis: Identifies and generates missing unit tests to meet coverage goals.
Acceptance Criteria Validation: Enforces that code meets documented business requirements (P0/P1/P2).
Pre-commit Quality Gates: Blocks commits that fail critical P0 acceptance criteria.
Use Case: Before committing code, run /compliance to automatically generate API documentation, create contract tests, ensure test coverage is above 80%, and verify that all "Must Have" acceptance criteria are met.

Quick Start

Run a full compliance scan across all APIs and code modules.

Frequently Asked Questions about compliance

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

FAQPage Schema

How do I automate API contract testing and enforce test coverage thresholds before commit?▼

API contract testing is automated by generating and validating OpenAPI specs and contract tests. The process enforces test coverage thresholds and blocks commits failing critical P0 acceptance criteria before code reaches production.

How do I validate code against business requirements and P0 acceptance criteria?▼

Validate code against business requirements by enforcing documented P0, P1, and P2 acceptance criteria. A compliance scan verifies all "Must Have" conditions are met and generates detailed compliance reports for non-compliant code.

Can I automatically generate missing unit tests to meet code coverage goals?▼

Missing unit tests can be automatically generated to meet code coverage goals. The compliance scan identifies gaps in existing test coverage and creates the necessary unit tests to enforce quality gates above 80%.

What is the best way to generate OpenAPI specs from existing code for compliance validation?▼

Generating OpenAPI specs for compliance validation is best handled by running an automated compliance scan. This process creates the API documentation, validates it via contract tests, and enforces pre-commit quality gates.

Does pre-commit quality gate validation work without external dependencies?▼

Pre-commit quality gate validation operates without external dependencies. It blocks commits failing critical P0 acceptance criteria by running local scripts and references to validate API specifications and test coverage.

Why should I block commits that fail P0 acceptance criteria during code validation?▼

Blocking commits that fail P0 acceptance criteria during code validation prevents non-compliant code from entering production. This ensures business requirements, API specifications, and test coverage standards are strictly met.