VibeRPGSimulator

Teaches the agent to write and review property-based tests with Hegel in Rust, Go, C++, TypeScript, Java and OCaml projects.

How it works

Foe: Bug Slime, a defect in your code.

Foes

  • Bug Slime

Party · Context

  • SentinelYour agent100/100

  1. Bug Slime

    The Bug Slime blocks the way.

    What really happensIt stands for a defect in your code.

    Sentinel: Context 100/100.

  2. Regress

    The Bug Slime uses Regress.

    What really happensA fix in one place breaks something that used to work.

    Sentinel takes 8. Sentinel: Context 92/100.

  3. Hegel property-based testing

    The hero equips the Hegel relic before writing a single test.

    What really happensThe hegel skill loads when you ask for property-based tests, or when the project already uses proptest, fast-check or a similar library.

    Bug Slime takes 21.

  4. Hegel property-based testing

    It reads the code's own promises before choosing where to strike.

    What really happensIt learns the Hegel API from existing tests and the installed library, and grounds each property in docs, signatures, asserts or a plain round trip.

    Bug Slime takes 18.

  5. Regress

    The Bug Slime uses Regress.

    Sentinel takes 8. Sentinel: Context 84/100.

  6. Hegel property-based testing

    Thousands of random blows find the weak spot, then shrink it to one.

    What really happensIt writes one property per test and runs thousands of cases. Hegel shrinks any failure to a minimal counterexample.

    Bug Slime takes 42.

  7. Hegel property-based testing

    A fresh ally studies the code without seeing the hero's tests.

    What really happensA separate subagent gets the code and its contract but not the tests, and returns properties and input classes that were missed.

    Adversarial reviewer: Context 40/40.

  8. Hegel property-based testing

    The summons work the problem, each in its own context.

    What really happensEach subagent does its own model and tool work, apart from the main conversation.

    Bug Slime takes 9.

  9. Hegel property-based testing

    Adversarial reviewer returns with a short report.

    What really happensOnly the subagent's final summary comes back to the main agent.

    Sentinel takes 2. Sentinel: Context 82/100. Sentinel: Insight. Adversarial reviewer returns.

  10. Hegel property-based testing

    The hero checks every test against the review list.

    What really happenshegel-review flags narrowed generators, fixed inputs, weak oracles, tolerance hacks and skipped tests, and gives the smallest fix.

    Bug Slime takes 10. Sentinel: Ward. Bug Slime falls.

  11. Victory

    The Bug Slime falls.

Learn this spell

Claude Code

/plugin marketplace add hegeldev/hegel-skill
/plugin install hegel-skill@hegeldev

Codex

$skill-installer install https://github.com/hegeldev/hegel-skill/tree/main/skills/hegel

Notes

Two skills: hegel writes the tests and hegel-review checks them for narrowed generators, weak oracles and tolerance hacks. The project needs the Hegel library for its language, and the skill learns its API from existing tests and the installed copy, so an offline arena works only when that library is already there. Before finishing, a separate subagent looks for missed properties. Codex: $skill-installer install https://github.com/hegeldev/hegel-skill/tree/main/skills/hegel adds the hegel skill only.

This spell has no recorded sessions in the curator's logs. Tried it? Send a spell report.