editorbridge-document-patch

# EditorBridge Document Patch Use this skill when the user asks for a document-wide edit in MarkEdit, Textastic, TextEdit, or iA Writer. Prefer native tools named `editor_*` when available. If native tools are unavailable, use the `editorbridge-mcp` server with the same tool names. Workflow: 1. Call `editor_check_permissions` when permission status is unknown. 2. Call `editor_snapshot` before proposing or applying a whole-buffer mutation. 3. Use the snapshotted text as the source of truth. Do not infer file identity from a window title when `path` is absent. 4. Prefer `editor_preview_patch` with `unified_diff` or literal patch hunks before mutation. 5. Explain the intended edit briefly when the user has not already approved the exact change. 6. Call `editor_apply_patch` with `snapshot_id` after verifying the patch preview. 7. If a full replacement is unavoidable, call `editor_apply_text` with `snapshot_id`. 8. Read the document again and verify that the expected edit landed. 9. Use `editor_restore_snapshot` if the applied result is wrong and a restore is safe. Never call `editor_apply_text` without `snapshot_id` unless the user explicitly accepts the no-snapshot risk. Treat stale snapshot errors as a stop condition, then capture a new snapshot and re-plan.