hegel

Guide property-based testing with Hegel by generating inputs and shrinking failures.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/vemolista/dotfiles --skill hegel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hegel
Source: https://github.com/vemolista/dotfiles/tree/main/dot_config/agents/skills/hegel
Command: npx skills add https://github.com/vemolista/dotfiles --skill hegel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides developers to implement property-based testing using Hegel by generating diverse inputs and shrinking failing cases.

Core Features & Use Cases

  • Generative testing guidance: learn to craft tests that produce meaningful counterexamples and automatic shrinking to minimal failing inputs.
  • Cross-language applicability: applicable to Rust and other Hypothesis-powered ecosystems, with integration into common runners like cargo test, pytest, and jest.
  • Workflow & porting guidance: provides references, evolving-test patterns, and property-category guidance to evolve existing tests into robust PBT workflows.

Quick Start

Start by writing tests that draw inputs with tc.draw() and assert properties to exercise your code paths.

Frequently Asked Questions about hegel

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

FAQPage Schema
How do I turn existing tests into property-based tests?

You evolve existing tests into property-based tests by drawing diverse inputs with tc.draw(), asserting properties across code paths, and using provided property-category guidance to structure the workflow.

How does shrinking work in property-based testing?

Shrinking automatically reduces failing generated inputs to their minimal failing counterexamples. Hegel guides crafting tests that produce meaningful counterexamples through automatic shrinking to minimal failing inputs.

Can I use property-based testing with cargo test, pytest, and jest?

Yes, property-based testing using Hegel integrates into common runners including cargo test, pytest, and jest across Rust and other Hypothesis-powered ecosystems.

What is the best way to start writing property-based tests in Rust?

Start writing property-based tests in Rust by drawing inputs with tc.draw() and asserting properties to exercise code paths, leveraging provided references and property-category guidance to structure the tests.

Does property-based testing work outside of Rust?

Yes, property-based testing using Hegel is applicable to Rust and other Hypothesis-powered ecosystems, providing cross-language workflow and porting guidance for common test runners.

When should I not use property-based testing?

Avoid property-based testing when your code cannot accept diverse generated inputs or when automatic shrinking fails to produce meaningful minimal counterexamples for your specific logic.