test-provenance-guard

Analyze test suites to verify imports and exercise of production functions.

7|2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/mthines/agent-skills --skill test-provenance-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-provenance-guard
Source: https://github.com/mthines/agent-skills/tree/main/skills/test-provenance-guard
Command: npx skills add https://github.com/mthines/agent-skills --skill test-provenance-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Developers often write tests that do not truly exercise the production code, leading to false confidence in software correctness.

Core Features & Use Cases

  • Static Analysis: Detects tests that declare local copies or shadow exported functions, preventing misleading test results.
  • Mutation Testing: Sabotages production functions to verify if tests catch deliberate faults, ensuring genuine coverage.
  • Autonomous Self-Healing: Extracts inline logic from test files, declares and creates proper exports, and rewires callers to avoid duplicated code.
  • Use Case: When refactoring code, ensure that tests are correctly linked to actual production functions, not local or stub implementations.

Quick Start

Run the test-provenance-guard skill to identify and fix tests that do not correctly verify production code, improving confidence in your test suite.

Frequently Asked Questions about test-provenance-guard

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

FAQPage Schema
How do I verify that my tests actually exercise production code instead of local copies?

Verifying tests exercise production code requires static analysis to detect when tests declare local copies or shadow exported functions, preventing misleading test results and ensuring your tests genuinely validate the actual software implementation.

What is mutation testing and how does it verify test coverage?

Mutation testing verifies test coverage by deliberately sabotaging production functions to introduce faults, then checking if your test suite catches those deliberate errors, ensuring your tests provide genuine coverage and reliable software verification.

How do I fix tests that are using local or stub implementations instead of exports?

Fixing tests using local implementations requires autonomous self-healing to extract inline logic from test files, declare and create proper exports, and rewire callers to avoid duplicated code, ensuring tests correctly link to actual production functions.

When should I run test provenance analysis during code refactoring?

Run test provenance analysis during code refactoring to ensure that your tests are correctly linked to actual production functions, not local or stub implementations, maintaining reliable test coverage verification and preventing false confidence.

Why do my tests pass when the production code is broken?

Tests pass when production code is broken because they often do not truly exercise the production code, leading to false confidence; static analysis detects tests that declare local copies or shadow exported functions, preventing misleading test results.