Database Transactions
SkillDatabases & dataDefine transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Database Transactions skill
What this skill tells your AI
The instructions your AI receives, as published by hoangnguyen0403/agent-skills-standard in skills/database/database-transactions/SKILL.md and read by ahel’s review.
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.
References
Signals
- GitHub stars
- 565
- Forks
- 164
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
database-transactions- Source
- github.com/hoangnguyen0403/agent-skills-standard