Specification
- Skill ID
- aj-geddes/useful-ai-prompts/transaction-management
- Publisher
- aj-geddes
- Repository
- useful-ai-prompts
- Installs
- 0
- Files
- 10
- Synced
- Sep 23, 2026
How to use it
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
aj-geddes/useful-ai-prompts/transaction-managementInstalls these files- SKILL.md
- references/deadlock-prevention.md
- references/mysql-isolation-levels.md
- references/mysql-locking.md
- references/mysql-transactions.md
- references/postgresql-explicit-locking.md
- references/postgresql-isolation-levels.md
- references/postgresql-transactions.md
- scripts/validate-schema.sh
- templates/migration-template.sql
What this skill tells the agent
Transaction Management
Table of Contents
- Overview
- When to Use
- Quick Start
- Reference Guides
- Best Practices
Overview
Implement robust transaction management with ACID compliance, concurrency control, and error handling. Covers isolation levels, locking strategies, and deadlock resolution.
When to Use
- ACID transaction implementation
- Concurrent data modification handling
- Isolation level selection
- Deadlock prevention and resolution
- Transaction timeout configuration
- Distributed transaction coordination
- Financial transaction safety
Quick Start
Simple Transaction:
-- Start transaction
BEGIN;
-- Multiple statements
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
UPDATE accounts SET balance = balance + 100 WHERE id = 2;
-- Commit changes
COMMIT;
-- Or rollback
ROLLBACK;Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| PostgreSQL Transactions | PostgreSQL Transactions |
| MySQL Transactions | MySQL Transactions |
| PostgreSQL Isolation Levels | PostgreSQL Isolation Levels |
| MySQL Isolation Levels | MySQL Isolation Levels |
| PostgreSQL Explicit Locking | PostgreSQL Explicit Locking |
| MySQL Locking | MySQL Locking |
| Deadlock Prevention | PostgreSQL - Deadlock Detection: |
Best Practices
✅ DO
- Follow established patterns and conventions
- Write clean, maintainable code
- Add appropriate documentation
- Test thoroughly before deploying
❌ DON'T
- Skip testing or validation
- Ignore error handling
- Hard-code configuration values
More from aj-geddes
Use this skill in a project
Open any RiverX project, search the Skills panel for aj-geddes/useful-ai-prompts/transaction-management, and install it in one click.