go-beyond-service-transaction-boundary
Invoke when deciding where a database transaction belongs in a Go service — handler, unit-of-work wrapper, repository, or service method — making multiple service operations atomic, or untangling *sql.Tx passed through the call stack. Not for distributed transactions, sagas, or connection pooling.
Pinned to revision e4081cbb4d29, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/go-beyond-service-transaction-boundary/SKILL.md
- skills/go-beyond-service-transaction-boundary/test-prompts.json
Every link opens the file at its source, pinned to the revision this page describes.