write-endpoint

Implement Wolverine HTTP endpoints with preconditions, stateless handlers, and tests.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hpsgd/claude-marketplace --skill write-endpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-endpoint
Source: https://github.com/hpsgd/claude-marketplace/tree/main/plugins/engineering/dotnet-developer/skills/write-endpoint
Command: npx skills add https://github.com/hpsgd/claude-marketplace --skill write-endpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building robust HTTP endpoints in Wolverine requires consistent patterns for preconditions, a stateless handler, and test scaffolding to ensure reliability and maintainability.

Core Features & Use Cases

  • Scaffold endpoint classes with a LoadAsync precondition phase and a stateless Handle method that emits events.
  • Support for common RESTful patterns (Create, Get, List, Patch) with proper concurrency safeguards and return of typed responses.
  • Integrated testing workflow with unit tests for handlers and integration tests for HTTP round-trips.

Quick Start

Create a new endpoint by implementing LoadAsync for preconditions and a static Handle method, then wire up routes and write tests.

Frequently Asked Questions about write-endpoint

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

FAQPage Schema
How do I create a Wolverine HTTP endpoint with preconditions and tests in .NET?

Build a Wolverine HTTP endpoint by implementing LoadAsync for preconditions and a stateless Handle method that emits events, then wire up routes and write unit and integration tests to verify HTTP round-trips.

What is the best way to structure a Wolverine handler for RESTful patterns like create, get, list, and patch?

Structure a Wolverine handler by enforcing a clean Handle path for stateless command execution alongside LoadAsync validations, mapping responses to typed IResult objects to support create, get, list, and patch operations.

How do I add concurrency checks to a Wolverine and Marten .NET service?

Add concurrency checks to a Wolverine and Marten .NET service by validating preconditions in LoadAsync before emitting events, ensuring data integrity during concurrent create, get, list, and patch operations.

Does the Wolverine endpoint pattern support integration testing for HTTP round-trips?

Yes, the Wolverine endpoint pattern includes an integrated testing workflow with unit tests for handlers and integration tests to verify the complete HTTP round-trip cycle.

Why should I use LoadAsync for preconditions in a Wolverine HTTP endpoint?

Use LoadAsync for preconditions in a Wolverine HTTP endpoint to separate validation logic from the stateless Handle method, enforcing clean code paths, proper IResult mapping, and comprehensive testing.