quality-gates-evidence-contract

Generate tech-agnostic JSON evidence logs for quality gates with git artifacts.

8|2|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill quality-gates-evidence-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gates-evidence-contract
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/quality-gates-evidence-contract
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill quality-gates-evidence-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires json, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that the structured evidence log for quality gates, which attests to the quality of a project, is produced and verified with verifiable integrity during the commit phase.

Core Features & Use Cases

  • Commit Phase Integration: Used by software-engineers to produce the evidence log during the COMMIT phase.
  • Adversarial Review Support: Supports quality-gates-lens (reader) during the review process for verifiable evidence.
  • Tech-Agnostic Schema: Ensures the schema is technology-agnostic for wide applicability.
  • Falsification-Proof: The schema is designed to be falsification-proof, requiring verifiable evidence like Git SHA and file paths for tests, build, mutation, commits, and RED/GREEN integrity.

Quick Start

At COMMIT phase, produce and submit quality gates evidence for your code changes using the 'quality-gates-evidence-contract' Skill.

Frequently Asked Questions about quality-gates-evidence-contract

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

FAQPage Schema
How do I generate a falsification-proof quality gates evidence log for git commits?

To generate a quality gates evidence log, this Skill produces a tech-agnostic JSON record during the commit phase. It references verifiable git artifacts like file paths and commit hashes to ensure the attestation is falsification-proof.

What is a quality gates evidence contract and when do I need it?

A quality gates evidence contract is a structured JSON schema used to attest to project quality during the commit phase. You need it when your workflow requires verifiable integrity for tests, builds, and commits to prevent falsification.

Does the quality gates evidence schema work across different coding platforms?

Yes, the quality gates evidence schema is explicitly technology-agnostic for wide applicability across multiple coding assistance platforms. It relies on universal git artifacts like commit hashes and file paths rather than framework-specific formats.

How do I verify RED/GREEN test integrity in a commit evidence log?

You verify RED/GREEN test integrity by checking the JSON evidence log generated at the commit phase. The schema requires references to verifiable git artifacts, ensuring the test, build, and mutation records cannot be falsified.

Do I need json and git utilities to produce verifiable commit evidence?

Yes, you require both json and git utilities to produce the falsification-proof records. The evidence log is generated as a JSON file and uses git commit hashes and file paths to anchor the quality attestation to verifiable artifacts.