What problem does it solve? Managing Keyboard Maestro macros as plain files under version control is error-prone: manual imports create duplicate macros under new UIDs, GUI edits drift out of sync with source files, and silent failures occur when the KM Engine is not running. This Skill encodes the exact workflows and pitfalls for keeping macros in the Chezmoi-Managed group synchronized with chezmoi. ## Core Features & Use Cases - Edit-and-apply workflow: Edit a .kmmacros plist in the chezmoi source, run chezmoi apply, and let the run_onchange hook invoke km-apply to delete the old macro by UID and re-import the new one. - GUI edit capture: Run km-export to write live macro XML back into the chezmoi source, stripping churn-prone date fields and refusing to overwrite files with uncommitted git changes. - Live state inspection: Read macro XML, delete, disable, or rename macros via osascript against the Keyboard Maestro AppleScript interface. - Use Case: You tweaked a macro in the Keyboard Maestro Editor and want it committed to your dotfiles repo — run km-export, then chezmoi apply and commit, without losing in-progress source edits. ## Quick Start Ask the assistant to add a new Keyboard Maestro macro to the Chezmoi-Managed group by generating a fresh UID and writing the .kmmacros file in the chezmoi source.
