/database-transactions

Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.

hoangnguyen0403@hoangnguyen0403

GitHub

From plugin

agent-skills-standard

538200 skills1 MCP

Install

$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill database-transactions --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/database-transactions

Context preview

The summary Claude sees to decide when to auto-load this skill.

Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.

SKILL.md

database-transactions.SKILL.md

name: database-transactions
description: Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
metadata:
  triggers:
    keywords:
    - transaction
    - consistency
    - idempotency
    - lock
    - concurrent write

Database Transactions

Priority: P0 (CRITICAL)

One business action should have one clear consistency strategy.

Rules

Define the unit of work before choosing transaction scope.
Keep transaction bodies short and purposeful.
Record isolation, lock, retry, and idempotency expectations for contested writes.
Split eventually consistent workflows from truly atomic ones.

Verify

[ ] Transaction boundary matches one business action.
[ ] Isolation or locking tradeoff is explicit.
[ ] Retry and idempotency behavior is defined for duplicate or concurrent requests.
[ ] External side effects are not hidden inside a DB transaction without compensation.

Anti-Patterns

**No giant transaction scripts**: long units increase contention and failure blast radius.
**No retry without idempotency**: duplicate writes become correctness bugs.
**No mixed atomicity story**: define what is immediate vs eventual.