hex-validate

Derive behavioral specs, run property and smoke tests, and write weighted verdict reports.

4|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/gaberger/hex --skill hex-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hex-validate
Source: https://github.com/gaberger/hex/tree/main/.claude/skills/hex-validate
Command: npx skills add https://github.com/gaberger/hex --skill hex-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates post-build semantic validation to catch bugs that slip through compile-lint-test pipelines, helping teams deliver more reliable software.

Core Features & Use Cases

  • Behavioral spec derivation from user-problem statements to define expected system behaviors.
  • Property tests, smoke tests, and sign-convention audits that produce a conclusive PASS/FAIL verdict.
  • Verdict reporting with a weighted score and a formal docs/validation-verdict.md artifact for traceability.

Quick Start

Provide problem_statement and paths to the generated domain code and tests, then run the validation to obtain a verdict.

Frequently Asked Questions about hex-validate

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

FAQPage Schema
How do I catch bugs that slip through compile-lint-test pipelines?

Post-build semantic validation catches bugs that slip through compile-lint-test pipelines by deriving behavioral specs from your problem statement, running property and smoke tests, and auditing sign conventions to produce a weighted PASS/FAIL verdict.

What is post-build semantic validation for software testing?

Post-build semantic validation is a software testing technique that derives behavioral specs from a problem statement and executes property tests against generated domain code to catch bugs missed by standard compile-lint-test pipelines.

How do I generate a validation verdict report from behavioral specs?

To generate a validation verdict report, provide a problem statement and paths to your domain code and tests. The validation process derives behavioral specs, runs property tests, and writes a weighted verdict to docs/validation-verdict.md.

Does semantic validation work with generated domain and test artifacts?

Yes, semantic validation is applied to codebases with generated domain and test artifacts. You provide the paths to these artifacts along with a problem statement to execute a predefined validation plan and obtain a verdict.

What's the best way to audit sign conventions in a software codebase?

Auditing sign conventions is best handled through post-build semantic validation. It executes a predefined validation plan against your domain paths to detect sign convention errors and includes the results in a formal weighted verdict report.