checkout-debug

Installation
SKILL.md

Checkout debug

Start with the reported failing action and its intended result, and keep the accepted offer and platform. Then find the boundary where things first diverge: the selected merchandise, the rendered UI, the submitted request, the persisted commerce record or the return state. Deliver the smallest justified repair, or a precise repair specification when you have no code or configuration access.

Two habits prevent most self-inflicted damage. Fixing a renderer must not replay a successful cart add. Missing confirmation must not become another payment. Before retrying anything, read back what already happened.

When the evidence is a funnel ratio, not a failing action

"People add to cart but don't buy" names a gap, not a fault.

Split it first. Cart → checkout started and checkout started → paid point to different places: the cart page or drawer, versus the payment form, processor and terms.

Walk the route. Follow the buyer's actual ad link on the affected phone, with the reported variant, quantity, cart surface and address region. Include quantity two when quantity handling is in question. Check whether payment fields mount and a rate exists for that route. A clean-link pass can miss a failure specific to the real entry. A completed test purchase checks more of the path, but is a real payment: perform it only within the owner's authorization or have the owner perform it, and report it as not done otherwise.

Allow for objections. If the route works, the gap may be an objection rather than a defect. Shipping that first appears at checkout, an unexpected currency or a missing delivery estimate produces the same drop with no bug. Say so, and hand the decision to the offer or support owner instead of "fixing" checkout. A lowish cart-to-paid ratio beside a healthy overall conversion rate may need no action. Processor approval problems belong to payment-network.

Read for the open task

Installs
157
GitHub Stars
37
First Seen
7 days ago