← GridlyCONTENT HISTORY
WHAT CHANGED
Update to Gridly
Snapshot Oct 31, 2026 · 12:11 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Gridly and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Make changes to many products, prices, stock levels, categories or coupons in a WooCommerce store safely. Use whenever the owner asks to raise or lower prices, change stock or status, tag or categorise products, create a discount code, or undo or schedule such a change.",
"included_files": [],
"name": "safe-bulk-edit",
"skill_md_contents": "---\nname: safe-bulk-edit\ndescription: Make changes to many products, prices, stock levels, categories or coupons in a WooCommerce store safely. Use whenever the owner asks to raise or lower prices, change stock or status, tag or categorise products, create a discount code, or undo or schedule such a change.\n---\n\nEvery Gridly change tool works in two steps. Never skip the first.\n\n1. **Preview.** Call the tool (`update_products`, `create_coupon`, `update_order`, `apply_product_content`) WITHOUT `confirm`. Nothing changes yet. You get a `preview_id`.\n2. **Show it.** Show the owner the preview plainly: how many items, the old and new values for the first few, and anything skipped. If the filter looks too broad (for example it includes products the owner did not mean), say so and offer to narrow it.\n3. **Ask for a clear yes.** Only after the owner explicitly approves, call the same tool again with `confirm: true` and the `preview_id`.\n4. **Report.** Say what was done and give the change number. Tell the owner they can say \"undo change N\".\n\nRules:\n- Never invent a `preview_id`. Previews expire after 15 minutes; if one expired, run the preview again.\n- To apply later instead of now, add `apply_at` (the store's local time, `YYYY-MM-DDTHH:MM`) to the confirm call. Use `list_scheduled_changes` and `cancel_scheduled_change` to manage them.\n- To reverse a change, call `undo_change` with the change number and follow the same preview-then-confirm steps. Use `change_history` to find numbers.\n- Refunds and payments cannot be made with Gridly. If asked, say so and point to WooCommerce itself.\n"
}SHA-256 of public snapshot: 950aaa29088cede336d91d1dd83ace9dab7e26e1fb3240799d0f0c17ec167291