skills.rest
erikshafer
erikshaferCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

marten-wolverine-aggregates

Write and review command handlers for Marten event-sourced aggregates with Wolverine atomic commits.

Updated Apr 21, 2026
Search Tags:#event sourcing#marten#wolverine#command handling#aggregate handlers
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill marten-wolverine-aggregates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: marten-wolverine-aggregates
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/marten-wolverine-aggregates
Command: npx skills add https://github.com/erikshafer/CritterCab --skill marten-wolverine-aggregates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Marten, Wolverine, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the creation and review of command handlers for event-sourced aggregates, leveraging Marten and Wolverine to ensure atomic commits of events and integration messages.

Core Features & Use Cases

  • Aggregate Handler Creation: Facilitates writing handlers for loading, validating, and appending events to aggregates.
  • Atomic Commit: Ensures that events and messages are committed atomically to maintain data integrity.
  • Use Case: When developing a ride-sharing platform, use this Skill to create handlers for trip lifecycle events, ensuring that state changes are consistent and reliable.

Quick Start

Use the marten-wolverine-aggregates skill to create a handler for the 'TripStarted' event.

Frequently Asked Questions about marten-wolverine-aggregates

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

FAQPage Schema
How do I handle command validation for event-sourced aggregates in Marten?▼

Command validation for event-sourced aggregates in Marten is handled by writing Wolverine command handlers that load, validate, and append events to aggregates within an atomic commit.

How does Wolverine ensure atomic commits of events and integration messages?▼

Wolverine ensures atomic commits by coordinating the validation and appending of events and integration messages together, maintaining data integrity and consistency for event-sourced systems.

Do I need both Marten and Wolverine to manage event sourcing and command handling?▼

Yes, both Marten and Wolverine are required dependencies. Marten manages the event sourcing storage while Wolverine provides the command handling framework for validation and atomic event commits.

What is the best way to create a command handler for a trip lifecycle event?▼

Creating a command handler for a trip lifecycle event involves using this framework to load the aggregate, validate the command, and append events like TripStarted atomically to maintain consistent state.

When do I need atomic commits for event-sourced aggregate handlers?▼

Atomic commits for event-sourced aggregate handlers are needed in systems requiring high consistency and integrity, ensuring that events and integration messages are saved together or not at all.

Can I use this approach for systems requiring high consistency in event sourcing?▼

Yes, this framework specifically applies to systems that require high consistency and integrity for event-sourcing patterns by ensuring events and messages are committed atomically.

Related Skills

Explore More Software Engineering Skills→
dodygdodyg

dotnet-wolverine

Configure Wolverine messaging and Marten event sourcing in .NET applications.

Community
Intermediate
hpsgdhpsgd

write-handler

Implement Wolverine command handlers with aggregate loading and cascading messages.

Official
Advanced
erikshafererikshafer

wolverine-marten-automation

Automate committed domain event handlers in CritterCab using Wolverine and Marten.

Community
Advanced
XyrcesXyrces
2

Event Systems

Design ECS event systems for Godot games using observer patterns.

Community
Advanced