npx skills add smithery/aj-geddes --skill transaction-management
aj-geddes/useful-ai-prompts
transaction-management
Manage database transactions for data consistency. Use when implementing ACID compliance, handling concurrency, or managing transaction isolation levels.
Installation
npx skills add aj-geddes/useful-ai-prompts --skill transaction-management
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
How WAL mechanics, checkpointing, concurrency rules, recovery work in tursodb
1.1K installsSubmit a transaction to Sumsub Transaction Monitoring (KYT) via the ApplicantResource API. TRIG…
20 installsChecks transaction scope, missing rollback handling, long-held transactions, trigger/notify int…
370 installsThis skill should be used when building apps that submit raw EVM transactions, custom contract …
368 installsThis skill should be used when the user wants to "submit a transaction", "execute calldata", "s…
364 installsThis skill should be used when the user asks to "send tokens", "transfer ETH", "send USDC to", …
359 installsAlso in this package
Other skills from aj-geddes/useful-ai-prompts · top by installs.
npx skills add aj-geddes/useful-ai-prompts
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,179 B -
docs
SUMMARY.md2,134 B
History
- First seen on skills.sh
- First recorded snapshot · 440 installs
SKILL.md
Transaction Management
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#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](references/postgresql-transactions.md) | PostgreSQL Transactions |
| [MySQL Transactions](references/mysql-transactions.md) | MySQL Transactions |
| [PostgreSQL Isolation Levels](references/postgresql-isolation-levels.md) | PostgreSQL Isolation Levels |
| [MySQL Isolation Levels](references/mysql-isolation-levels.md) | MySQL Isolation Levels |
| [PostgreSQL Explicit Locking](references/postgresql-explicit-locking.md) | PostgreSQL Explicit Locking |
| [MySQL Locking](references/mysql-locking.md) | MySQL Locking |
| [Deadlock Prevention](references/deadlock-prevention.md) | 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