sim-review

Review coordination, gossip, and pipeline code for deterministic simulation testing compliance.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ahrav/Gossip-rs --skill sim-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sim-review
Source: https://github.com/ahrav/Gossip-rs/tree/main/.claude/skills/sim-review
Command: npx skills add https://github.com/ahrav/Gossip-rs --skill sim-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces deterministic simulation testing (DST) compatibility in coordination, gossip, and pipeline code, ensuring that critical system components can be reliably tested in-process without external dependencies.

Core Features & Use Cases

  • DST Compliance Enforcement: Verifies code adheres to patterns for simulation-testability, using evidence from FoundationDB, sled, Firezone, and more.
  • Targeted Code Review: Focuses on coordination, gossip, and pipeline modules, identifying violations of DST principles like direct clock reads, direct I/O, and non-deterministic iteration.
  • Use Case: Before merging changes to the shard lifecycle or gossip protocols, run this Skill to guarantee that the new code can be effectively tested using seeded PRNGs and simulated clocks, preventing subtle bugs in production.

Quick Start

Run the sim-review skill on the modified files in the gossip-coordination directory.

Frequently Asked Questions about sim-review

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

FAQPage Schema
How do I enforce deterministic simulation testing compatibility in coordination and gossip codebases?

To enforce deterministic simulation testing (DST) in coordination, gossip, and pipeline codebases, you must abstract I/O, control randomness, and manage time as input behind synchronous traits for in-process testability.

What makes code fail deterministic simulation tests when modifying shard lifecycle or gossip protocols?

Code fails deterministic simulation tests by violating DST principles through direct clock reads, direct I/O operations, and non-deterministic iteration, which break in-process testability.

How do I review code for DST compliance using FoundationDB and TigerBeetle principles?

Reviewing code for DST compliance involves validating adherence to principles derived from FoundationDB and TigerBeetle, ensuring strict synchronous trait methods, pure state transitions, and side-effect abstraction.

Can I use deterministic simulation testing for pipeline modules without external dependencies?

Yes, you can test pipeline modules without external dependencies by enforcing strict adherence to synchronous trait methods and abstracting side-effects behind traits for reliable in-process simulation.

Why does my seeded PRNG simulation fail on non-deterministic iteration in gossip protocols?

Seeded PRNG simulations fail because non-deterministic iteration introduces uncontrolled variance, violating DST principles that require pure state transitions and abstracted side-effects for deterministic execution.

What are the limitations of sim-review for testing distributed systems?

The sim-review approach is limited to validating DST compatibility in coordination, gossip, and pipeline codebases, requiring synchronous trait methods and strict side-effect abstraction to function correctly.