Check your add-on customisations before updating the add-on
You find out before an update which customisations might break, instead of finding out on the live shop.
What it replaces: 1-2 h of comparing files per update
What you write to Claude
„We're updating ps_facetedsearch and ps_shoppingcart. List our theme overrides for both, compare them with the current module templates, and tell me what might break.”
The problem
We updated an add-on last year and the product page broke because our customised copy of its layout was out of date.
What Claude does
- Claude lists the add-ons and the customised copies of their layouts in your theme.
- It reads those copies.
- It flags what the new version may have changed.
- It proposes fixes, saved only after your approval.
What you get
A pre-update list of customisations at risk and the fixes to make, before anything breaks on the live shop.
You stay in control
Claude only reads. Nothing in your shop changes. Changes to the shop's look use a separate, extra-protected connection, usually set up by whoever looks after your shop.
Related use cases
- Check shop health before an update
- Change how an add-on looks without losing it on the next update
- Find out which add-on shows a box on the page
For developers
- Area
- 3 · Appearance & deployments
- Connector
- service connector
- In the free Audit
- no, paid version only
- For
- Agency / freelancer, Developer
- Tools
- ps_list_modules, ps_list_theme_files, ps_read_theme_file, ps_check_shop_health, ps_module_file
Step by step
- Lists module versions with ps_list_modules and overrides with ps_list_theme_files (path modules/).
- Reads the overrides with ps_read_theme_file. The module's own current templates can be read for comparison with ps_module_file (action read) when Modules (block 4) is on.
- Compares variables, blocks and includes, and flags anything the new version may have renamed.
- Proposes override changes, applied only after a diff preview and your approval.
Safety
Block 3 works only through the service connector: a separate token accepted only from allowlisted IP addresses, off after installation. Claude changes the module's look through a template override in your theme (ps_override_module_template), so a module update leaves it alone. The override is a theme file, backed up before every write and restorable with ps_restore_file_backup. If the change could only be made inside the module itself, Claude says so: direct edits of module files are possible in Modules (block 4, ps_module_file, with backup), but a module update erases them. Run the update on a staging domain first; staging domains are free on every licence.
Last updated: 2026-10-05