invariant-test

Derive mutation-validated surface tests from service invariants.

11|Updated Sep 5, 2025

Search Tags:#adr #concurrency #reliability #invariants #test-automation #mutation-testing #surface-testing

Ready to run

npx skills add https://github.com/thrawn01/claude-dotfiles --skill invariant-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: invariant-test
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/invariant-test
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill invariant-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Derives surface tests from a service's stated invariants (ADRs, load-bearing doc comments) and proves they fail when invariants are violated.

Core Features & Use Cases

Mutation-validated test generation from invariants to detect violations that other suites miss
Phase-driven workflow including ledger, consequence derivation, and mutation validation
Surface-testing oriented outputs with a publishable invariant-test.html report

Quick Start

Run invariant-test to derive surface tests from a service's invariants and validate them via mutation testing.

Frequently Asked Questions about invariant-test

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

FAQPage Schema

How do I generate tests that verify system invariants under race conditions?▼

You can derive mutation-validated surface tests from stated invariants to reveal violations. This targets invariants that guard correctness under race and timing in concurrent systems.

What is mutation-validated surface testing for concurrent systems?▼

Mutation-validated surface testing derives tests from service invariants and proves they fail when invariants are violated. It detects violations that other test suites miss in concurrent systems.

Can I use ADRs and doc comments to generate automated tests for concurrency reliability?▼

Yes, you can derive surface tests from invariants stated in ADRs and load-bearing doc comments. The workflow applies to concurrent systems described by these tech specs.

How do I start deriving invariant tests from my repository codebase?▼

Run the invariant-test process to derive surface tests from service invariants and validate them via mutation testing. You need repository codebase access, ADRs, and the ability to run the test suite.

Does invariant testing require an observability surface to record results?▼

Yes, the process requires an observability surface to record results. It outputs a publishable invariant-test.html report alongside a phase-driven workflow including ledger and consequence derivation.

What are the limitations of deriving tests from invariants for concurrent systems?▼

The process requires access to the repository codebase, ADRs or doc comments, and the ability to run a test suite with mutation validation. It targets invariants guarding correctness under race and timing conditions.