pact-module-validation

Coordinate four-phase Pact module validation across REPL analysis, execution, devnet deploy, and verification.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill pact-module-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pact-module-validation
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/pact-module-validation
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill pact-module-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end validation of Pact modules to catch defects early, reduce deployment risk, and ensure contract integrity.

Core Features & Use Cases

  • Four-phase validation protocol: REPL analysis, REPL execution, devnet deploy, devnet verification.
  • Traceability and evidence collection via a validation report template.
  • End-to-end lifecycle testing including governance-like flows and cross-module interactions.

Quick Start

Run the four-phase Pact module validation protocol on a target module to verify quality.

Frequently Asked Questions about pact-module-validation

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

FAQPage Schema
How do I validate a Pact module before deploying to devnet?

Pact module validation uses a four-phase protocol covering REPL analysis, REPL execution, devnet deploy, and devnet verification to ensure reliability and contract integrity. It automates end-to-end checks to catch defects early and reduce deployment risk.

What is end-to-end Pact module testing and how does it work?

End-to-end Pact module testing coordinates REPL analysis, REPL execution, devnet deploy, and devnet verification to enforce deterministic testing steps and reproducible deployment checks across module lifecycles. It reduces deployment risk by catching defects early.

Can I trace and reproduce Pact module validation results for QA purposes?

Pact module validation enforces traceability and evidence collection via a validation report template. The four-phase protocol collects deterministic testing results and ensures reproducible deployment checks across the module lifecycle for QA purposes.

Does Pact module validation support governance flows and cross-module interactions?

Pact module validation includes end-to-end lifecycle testing covering governance-like flows and cross-module interactions. The four-phase protocol ensures contract integrity and reduces deployment risk across these complex module interactions.

What are the limitations of automating Pact module validation?

Pact module validation is limited to its four-phase REPL and devnet protocol enforcing deterministic testing steps. It focuses on module lifecycle checks, contract integrity, and reproducible deployment verification without extending beyond this defined scope.

Do I need a devnet environment to run Pact module validation?

A devnet environment is required for the deploy and verification phases of Pact module validation. The four-phase protocol spans REPL analysis, REPL execution, devnet deploy, and devnet verification to ensure end-to-end module reliability.