More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    WordPress Safe Updates That Catch a Broken Checkout

    1

    Update WordPress plugins, themes and core without breaking checkout: backup checked first, risky updates one at a time, rollback.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    WordPress Safe Updates That Catch a Broken Checkout

    WordPress Safe Updates That Catch a Broken Checkout

    Example session with this skill installed

    Please run this month's updates on my WooCommerce store: plugins, themes and WordPress core. It's a local copy running at http://localhost:8181. WP-CLI works with docker exec mystore-cli wp <command>, and you can get a shell on the server with docker exec -i mystore-cli sh -c '<command>' (WordPress lives in /var/www/html). I'm away from my desk, so don't wait for me to approve anything. Just do it carefully and tell me what happened.

    • Read your context and instructions
    • Compiled the wordpress safe updates

    I stopped the run early. Only one of the updates is done. A payment plugin update broke checkout, so I rolled it back and didn't apply the rest.

    What happened

    • I backed up the database and wp-content first and verified the backup. It's at wp-backups/mystore/20261013-122745. Uploads are not in it.
    • I took a baseline of the site while it was working normally.
      akismet 5.7 → 5.7.2 updated and passed the store check.
      acme-pay-gateway 1.0.0 → 1.0.1 removed the "acme_pay" card payment from checkout. Every page still returned 200, so only the checkout check caught it. It failed twice, so I rolled it back to 1.0.0.
    • After the rollback the checks passed, and I reopened the store. It's online, matches the baseline, and the card payment is offered again.
    • The cause is in the 1.0.1 code. It hides the gateway unless the acme_pay_merchant_region option has a value, and this store has none.

    Not applied

    • wp-mail-smtp 3.8.2 → 4.10.2
    • wordpress-seo 26.9 → 28.7
    • woocommerce 10.9.4 → 11.2.1
    • storefront 4.5.5 → 4.6.2, plus the inactive twentytwentyfour and twentytwentythree
    • WordPress core 7.0.5 → 7.0.7

    I stopped at the first failure, so none of these were tried. I read the changelogs for wp-mail-smtp and wordpress-seo and found nothing that blocks them. wp-mail-smtp's removed Sendinblue library doesn't matter, because the mailer here is plain "mail".

    Held on purpose

    • contact-form-7 6.1.1 → 6.2.2 needs WordPress 7.1.
    • WordPress core 7.1.3 is a major version, and you didn't give an explicit yes, so I didn't apply it.

    Your decision
    Set acme_pay_merchant_region to the right value for your Acme Pay account. Then either re-update acme-pay-gateway or ask me to run the remaining updates. I haven't set it, because I don't know the correct value.

    What this run didn't prove
    No order was placed, so the final "Place order" click is untested. The report is in wp-runs/mystore-2026-10-13/report.md.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem. Update night is where WordPress stores break. You click "update all", every page still loads, and a payment plugin has quietly stopped offering card checkout. You find out from a customer, or from the orders that stopped coming in. Doing it carefully by hand (backup, one plugin at a time, check checkout after each) is slow enough that it gets skipped. This skill has your coding agent do the careful version: a checked backup first, risky updates one at a time with a checkout check after each, the one plugin that broke something rolled back, and a plain report of what happened.

    What it does. You type "run this month's updates on my WooCommerce store" and step away. The agent backs up the database and plugin files, copies the backup to your machine and checks it is complete, records how the store looks when healthy, then applies updates. In the example run above, a payment plugin update removed the card payment from checkout while every page still returned 200. The checkout check caught it, the agent rolled back that one plugin, confirmed the store matched its starting state, reopened it and stopped, leaving the rest for your decision.

    • A plan before any change: what is safe to batch, what goes one at a time (major versions, payments, cart, shipping, tax, pricing, translations) and what is held because it needs a newer WordPress or PHP, so you see the risk before anything moves.
    • No verified backup, no changes, so a rollback always has a real copy to roll back to.
    • Maintenance mode kept on while it works. WordPress turns it off after every plugin update; the skill turns it back on and checks from outside, so the store does not quietly reopen halfway through.
    • Checkout checked after each risky update: payment methods, shipping, tax, currency and products, so a plugin that breaks checkout while every page loads gets caught.
    • Only the plugin that broke gets rolled back, then the store is re-checked and reopened once it matches its starting state, so one bad release means one rolled-back plugin and a note in the report.
    • WooCommerce updated alone with its database step, core pinned to the version you approved, so nothing jumps a major version you did not ask for.
    • A plain report: what changed, what was held and why, what needs you, and what the run did not prove, ready to forward to a client.

    Why this beats prompting it yourself.

    Ask a capable agent to "run this month's updates" without this skill and it tends to:

    • Leave the store open to shoppers for the whole run.
    • Keep one unchecked backup on the same server it is updating.
    • Ship a checkout with no card payment and report the gateway as "still enabled".

    With the skill, the agent:

    • Closes the store, re-closes it after every update, and checks from outside.
    • Checks the backup is complete and copies it to your machine first.
    • Checks what checkout actually offers and rolls back the plugin that broke it.

    Known limitations. WordPress sites and hosting vary, and the safeguards are instructions your agent follows, not locks: test on a staging copy first and keep your own backups. It never places an order, so the final "Place order" click is not tested. It checks the pages you list plus shop, a product and cart; logged-in areas and JavaScript features are not exercised. File backup and rollback need shell access to the server. It does not restore a database, because that erases orders placed since the backup. Terminal agents only (Claude Code, Codex CLI and similar), with WP-CLI access to each site.

    What's inside. SKILL.md (the rules, procedure and report format), scripts/wpsu.py (plan, backup, baseline, check, maintenance, rollback, cache and changelog commands; Python 3 standard library), references on the WordPress behaviors behind each step and every setting in the sites file, an example sites file and an example of a run that caught a broken update. Per site you can add pages to check, plugins to always isolate, updates to hold with a reason, your cache commands and a staging copy to run first.

    $12. Pays for itself the first time it rolls back an update that broke checkout, instead of you hearing about it from a customer.

    • It never places an order, so the final "Place order" click is not tested; payment methods are checked without a cart or customer address.
    • It checks the pages you list plus shop, a product and cart. Logged-in areas, translated pages and JavaScript features such as maps or sliders are not exercised.
    • File backup and plugin rollback need shell access to the server. Without it, rollback works only for wordpress.org plugins and you need your host's backup.
    • It does not restore a database. That decision stays with you, because a restore erases orders placed since the backup.
    • Safeguards are instructions your agent follows. Test on staging first and keep your own backups.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Wordpress
    Python

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    api.wordpress.org

    File Scopes

    wp-sites.json
    wp-backups/**

    no credentials stored or read, no environment variables read, nothing installed. The scan's network warning is the page and changelog checks above. The description is over claude.ai's 200-character upload limit on purpose: the skill needs a terminal agent and does not run in claude.ai.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    It works in agents that can run terminal commands, such as Claude Code and Codex CLI. It does not work in chat-only apps, including claude.ai on the web, because it has to run WP-CLI.

    WP-CLI access to the site: SSH (most managed hosts offer it), a local install, or Docker. Shell access adds file backups and plugin rollback.

    It shows the plan first and waits for your go unless you tell it not to wait. WordPress core major versions always need an explicit yes. Point it at your staging site first.

    It re-checks once (a fault right after an update can clear by itself), then rolls back that one plugin from the backup it took, checks the store again, reopens it if it matches the starting state, stops, and tells you what failed.

    Yes. List them in the sites file. It finishes one site completely before starting the next and stops the run at the first failure.

    New in E-commerce