meridian-code-review

Review Meridian .NET/F# code for architecture compliance and storage integrity.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meridian-code-review
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.agents/skills/meridian-code-review
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Meridian’s codebase spans pipelines, storage durability, providers, and dual UI surfaces, which makes it easy to introduce subtle correctness, performance, and architecture regressions during changes.

Core Features & Use Cases

  • Architecture-compliant code reviews: Applies Meridian’s MVVM, dependency graph, and cross-project rules to C# and F# changes.
  • Durability and integrity checks: Enforces storage/WAL correctness invariants such as AtomicFileWriter usage, WAL flush ordering, and IFlushable shutdown flow.
  • Provider and backfill compliance: Validates provider resilience, CancellationToken propagation, reconnect expectations, and ProviderSdk interface adherence.
  • Quality-gated test reviews: Detects xUnit async void tests, timing anti-patterns, shared mutable state, and other reliability issues.

Quick Start

Use the meridian-code-review skill when you want an evidence-focused review and refactoring plan for Meridian C# or F# code related to MVVM, pipelines, providers, backfill, storage, WAL, or test quality.

Frequently Asked Questions about meridian-code-review

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

FAQPage Schema
How do I review Meridian .NET code for architecture compliance and WAL integrity?

Review Meridian .NET code for architecture compliance and WAL integrity by applying seven deterministic lenses covering MVVM, pipeline performance, provider compliance, and storage invariants like WriteAheadLog ordering and AtomicFileWriter enforcement.

What is the best way to check MVVM refactor correctness in Meridian C# and F# pull requests?

Check MVVM refactor correctness in Meridian C# and F# pull requests by validating cross-project dependency graphs and architecture rules against Meridian namespaces and contracts like IMarketDataClient and IStorageSink.

How does WriteAheadLog flush ordering affect IFlushable shutdown flow in Meridian storage?

WriteAheadLog flush ordering affects IFlushable shutdown flow by enforcing storage durability invariants; incorrect ordering risks data loss, so code reviews verify AtomicFileWriter usage and proper shutdown sequencing.

Can I use automated code review to detect xUnit async void tests and timing anti-patterns in Meridian?

Automated code review detects xUnit async void tests, timing anti-patterns, and shared mutable state in Meridian by applying quality-gated test reviews that identify reliability issues across C# and F# test suites.

Does Meridian code review validate CancellationToken propagation and ProviderSdk interface adherence?

Meridian code review validates CancellationToken propagation and ProviderSdk interface adherence by checking provider resilience, reconnect expectations, and backfill compliance across single-file and multi-file PR-level changes.

What are the limitations of reviewing Meridian code without enforcing AtomicFileWriter and IStorageSink contracts?

Reviewing Meridian code without enforcing AtomicFileWriter and IStorageSink contracts risks subtle correctness and durability regressions, as storage integrity invariants ensure proper WAL ordering and resilient shutdown flushing.