backend-concurrency-idempotency-validation

Validate backend concurrency behavior to prevent duplicate mutations and lost updates.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill backend-concurrency-idempotency-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-concurrency-idempotency-validation
Source: https://github.com/belluga/delphi-ai/tree/main/skills/backend-concurrency-idempotency-validation
Command: npx skills add https://github.com/belluga/delphi-ai --skill backend-concurrency-idempotency-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prove that backend behavior remains correct under real concurrent requests instead of assuming that ordinary functional tests or generic load tests will expose race conditions.

Core Features & Use Cases

  • Use for mutation endpoints, jobs, webhooks, reservation/purchase flows, exact-once semantics, or any path where duplicate or overlapping requests can corrupt state.
  • This skill complements runtime-load-stress-validation; it does not replace it.
  • Prefer safe non-production environments.

Quick Start

Run the deterministic concurrent probe against your mutation endpoints to collect evidence of race conditions.

Frequently Asked Questions about backend-concurrency-idempotency-validation

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

FAQPage Schema
How do I test backend API endpoints for race conditions and duplicate mutations?

Testing backend API endpoints for race conditions involves running deterministic concurrent probes against mutation paths to validate behavior and collect evidence of duplicate mutations or lost updates.

What is the best way to verify exact-once semantics under concurrent load?

Verifying exact-once semantics under concurrent load requires defining domain-level invariants and concurrency policies, then executing targeted probes to document and verify that overlapping requests do not corrupt state.

How do I validate webhook idempotency when overlapping requests occur?

Validating webhook idempotency involves applying deterministic probes to webhook flows to ensure exact-once semantics, defining invariants, and confirming that overlapping requests cannot corrupt backend state.

Does this concurrent probe approach replace standard API load testing?

No, this concurrent probe approach does not replace standard API load testing. It complements runtime-load-stress-validation by specifically proving correctness and preventing duplicate mutations under real concurrency.

Can I run race condition probes against production backend environments?

You should not run race condition probes against production. To safely identify duplicate mutations and validate behavior, prefer running deterministic concurrent probes in safe non-production environments.