Use when an operation changes multiple files, registrations, database rows, configs, versions, or external resources that must not be left half-updated.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add ShugokiFable/Ultimate-AI-Starter-Bundle --skill transactional-updates --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Transactional Updates?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/shugokifable-transactional-updates)More formats (shields.io, HTML) on the badges page.
---
name: transactional-updates
description: Use when an operation changes multiple files, registrations, database rows, configs, versions, or external resources that must not be left half-updated.
---
# Transactional Updates
## Core rule
A multi-step update needs an explicit commit boundary.
Validate prerequisites first. Snapshot or **backup** user-owned state that may need restoration. Prepare replacements in temporary locations, verify them, then publish using an **atomic** replace or the closest platform-supported equivalent.
For multiple resources, define the order and a transaction marker so recovery can distinguish old, staged, and committed states. Do not announce success before the final **commit** and read-back verification.
If a later step fails, roll back only what this operation owns; never overwrite newer external changes with a stale backup. If full rollback is impossible, record the partial state precisely and make rerun/resume deterministic.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
