prove-check

Validate test checks by ensuring they fail on targeted regressions.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/alexandersumer/config --skill prove-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prove-check
Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/prove-check
Command: npx skills add https://github.com/alexandersumer/config --skill prove-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that your local checks effectively catch regressions, providing a reliable way to validate the effectiveness of your tests, scripts, linters, or gates.

Core Features & Use Cases

  • Regression Testing: Validates that tests fail on the regressions they are intended to catch.
  • Proof Policy: Utilizes a strict proof policy to ensure that proofs are valid and not invalidated by changes.
  • Quick Start: Run the check with the specific scope and arguments to prove that it catches the intended regression.

Quick Start

Run the prove-check skill with the exact scope and arguments where you suspect a regression has occurred.

Frequently Asked Questions about prove-check

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

FAQPage Schema
How do I validate that my regression tests actually catch the intended software defects?

To validate regression tests, run the check with the specific scope and arguments where you suspect a regression has occurred to prove it fails on the targeted defect. This ensures your local checks effectively catch regressions.

What is test check effectiveness validation in software quality workflows?

Test check effectiveness validation is the process of ensuring your tests, scripts, linters, or gates fail on the regressions they are designed to catch. It provides a reliable way to validate software quality.

How do I verify my linters and scripts fail on the regressions they are designed to catch?

You verify linters and scripts by running the validation check with the exact scope and arguments of the suspected regression. This confirms the check fails as intended, ensuring code reliability.

Do I need a proof policy to validate test suite reliability?

Yes, you need a strict proof policy for test validation to ensure that proofs are valid and not invalidated by changes or updates. This policy accounts for changes to maintain software quality.

When should I use regression test validation for my local checks?

You should use regression test validation when you need to ensure your local checks effectively catch regressions before they reach production. It is suitable for test suite reliability in software development workflows.

What are the limitations of validating test checks without a proof policy?

Without a proof policy, test validation cannot ensure that proofs remain valid and are not invalidated by changes. This limits check effectiveness and reduces code reliability during software updates.