skills.rest
jamesaphoenix
jamesaphoenixCOMMUNITY
Explore all skills by this author →
Website𝕏@jamesaphoenix12GitHub

verify-invariants

Link tests and source annotations to verify design invariants via tx spec.

1|Updated Feb 20, 2026
Search Tags:#invariants#design-doc#harden#tx-spec#test-annotation#fci
One-click install
npx skills add https://github.com/jamesaphoenix/tx-agent-kit --skill verify-invariants
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-invariants
Source: https://github.com/jamesaphoenix/tx-agent-kit/tree/main/.claude/skills/verify-invariants
Command: npx skills add https://github.com/jamesaphoenix/tx-agent-kit --skill verify-invariants

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement and verify invariants defined in design documents by annotating tests and source code with [INV-*] and @spec tags, and by driving tx spec coverage from BUILD toward HARDEN (100% FCI).

Core Features & Use Cases

  • Annotate tests with [INV-*] to link invariants to test coverage.
  • Annotate source files with // @spec to enforce invariants in code.
  • Run tx spec discovery, fci checks, and matrix reports to track progress toward HARDEN.
  • Use case: validate that a design doc invariant is test-covered and enforceable in runtime behavior.

Quick Start

Install the tx tooling, initialize the workspace, and run the end-to-end invariants workflow from gaps to HARDEN.

Frequently Asked Questions about verify-invariants

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

FAQPage Schema
How do I verify design doc invariants are covered by tests and source code?▼

To verify design doc invariants, you link tests using [INV-*] annotations and source code using // @spec tags, then compute Full Coverage Index (FCI) progress to ensure invariants are documented, tested, and hardened.

What is the Full Coverage Index (FCI) for invariant testing?▼

The Full Coverage Index (FCI) is a computed metric tracking invariant verification progress from BUILD toward HARDEN (100% FCI), ensuring design document invariants are fully test-covered and enforceable in runtime behavior.

How do I annotate tests and source files to link design invariants?▼

Annotate tests with [INV-*] tags to link invariants to test coverage, and annotate source files with // @spec tags to enforce invariants in code across multiple languages and document types.

Can I use tx spec discovery to track invariant hardening progress across multiple languages?▼

Yes, tx spec discovery works across multiple languages and document types by discovering invariant links, running FCI checks, and generating matrix reports to track progress toward HARDEN.

What's the best way to harden design invariants end-to-end?▼

The best way to harden design invariants is running the end-to-end invariants workflow: discover invariant links via tx spec, annotate tests and source, compute FCI checks, and generate matrix reports tracking progress toward 100% HARDEN.

Related Skills

Explore More Software Engineering Skills→
santosomarsantosomar
1

abstract-invariant-generator

Generate abstract invariants for numerical C code using abstract interpretation domains.

Community
Advanced
AtyantikAtyantik
5

coverage-analyzer

Analyze coverage reports to identify uncovered lines and missing branches.

Official
Intermediate
haposofthaposoft
54

hapo:test

Automates execution and verification of unit, integration, e2e, and UI tests.

Official
Advanced
ArabelaTsoArabelaTso
142

abstract-trace-summarizer

Summarize program execution traces and behavior using abstract interpretation.

Community
Advanced