ecommerce-cia — Commerce Integrity Auditor
電商金流與系統完整性稽核 · a skill for Claude Code and OpenAI Codex
測試全綠，線上卻掉單、庫存鎖死、後台開關沒作用？
ecommerce-cia 盯的是錢和庫存真正走過的路 —— 從結帳、Callback、退款到後台，一條一條驗給你看。
Green tests, lost orders. ecommerce-cia audits the path money and stock actually take — and walks first-time builders through Taiwan's payment gateways from zero.
快速開始 Quick start · 串接稽核 Wiring audit · 抓到過什麼 What it catches · 支援金流 Providers · 常見問題 FAQ · 安裝 Install
claude plugin marketplace add mixocreative/ecommerce-cia && claude plugin install ecommerce-cia@mixocreative
你的商店上線了，測試也全過了。然後：客人付了錢訂單卻顯示「未付款」、過期訂單的退庫存把已付款訂單的庫存也退掉了、後台把 ATM 轉帳關掉了結帳頁照樣出現、藍新的 Callback 重送一次庫存就被釋放兩次。每一段程式單獨看都沒錯，錯在它們之間。
對 AI Agent 輸入 /ecommerce-cia，它會把結帳 → 金流 → Callback → 訂單 → 庫存 → 出貨 → 退款 → 後台整條路走一遍，在測試環境實際下單驗證，再交出一份每一條「通過」都附證據的報告。還沒串金流？它會切換成新手引導模式，一次問一個問題，帶你從零接好藍新、綠界或 LINE Pay。
Your shop is live and every test passed. Then a paid order shows "unpaid", the expiry job restocks an order that was already paid, the admin switched ATM transfer off but checkout still offers it, and one duplicate gateway callback releases the stock twice. Each piece is correct alone; the defect is between them. /ecommerce-cia walks checkout → gateway → callback → order → stock → fulfilment → refund → admin, places real sandbox orders, and reports nothing as passed without evidence from this run. No gateway yet? It switches to setup mode and walks you through NewebPay, ECPay or LINE Pay from zero.
Quick start｜快速開始
1. 安裝 Install（其他方式見 Install）
claude plugin marketplace add mixocreative/ecommerce-cia && claude plugin install ecommerce-cia@mixocreative
2. 直接對 Agent 下指令 Ask your agent — 複製任一則：
/ecommerce-cia 上線前稽核，Screen 等級
我要開一家網路商店，想用藍新收信用卡跟超商代碼，從零帶我串。
幫我確認：後台關掉的付款方式，結帳頁是不是真的不會出現？Callback 重送兩次會不會重複扣庫存？
我們的電商是自己寫的，下一步該稽核什麼？用參考系統當檢查清單，跑一次 Walk 等級的串接稽核。
/ecommerce-cia pre-launch audit: place one sandbox order per payment method,
then cancel and refund each, and show me the stock at every step.
3. 你會拿到什麼 What comes back
- 稽核模式 Audit：給老闆看的 5 行白話摘要（哪裡安全、哪裡危險、先做什麼），接著是每個步驟一行、每個發現附
檔案:行號 與引用程式碼，以及一張證據帳冊（PASS / FAIL / UNVERIFIED / UNPROVEN，每個 PASS 都指向這次執行產生的檔案）。
- 新手引導模式 Setup：一張準備就緒卡，每項前置需求 ✅ / ⏳ / ❌，附負責人、日期，以及每種付款方式的實機探針結果。
Feature list vs wiring audit｜功能清單 vs 串接稽核
A feature comparison asks: "Do we have refunds?" A wiring audit asks: "What happens if a payment succeeds, the callback is lost, stock changes, the invoice write fails, and the operator opens the order two days later?" That is where custom commerce engines break — and it is the question ecommerce-cia asks first, about your shop, and answers with evidence.
功能比較問的是：「我們有退款功能嗎？」串接稽核問的是：「如果付款成功、Callback 掉了、庫存變了、發票寫入失敗，而管理員兩天後才打開這張訂單，會發生什麼事？」 自己寫的電商系統就是在這裡出事。ecommerce-cia 第一個就問你的商店這個問題，並用證據回答。
Three layers, every run｜每次都檢查三層： function logic (each function correct on its own) · relationship wiring (every call made, every result persisted, retries and partial failures handled) · lifecycle business rules (the whole shop obeys its rules when events arrive late, twice or out of order). The report counts findings per layer — a report with only the first layer was not a wiring audit.
A side-by-side state map per lifecycle｜每個流程的對照狀態圖 — a mature reference (ProcessWire Commerce, WooCommerce, Shopify, Saleor) is used as a checklist of stages, never as the truth; your own rules, the gateway manuals, Taiwan invoice law and your architecture are the authority:
| Lifecycle｜流程 | Reference path｜參考系統 | Your path｜你的系統 | Failure / retry｜失敗與重試 | Operator sees｜後台看到 |
|---|
| Checkout 結帳 | cart → order → payment | cart → locked stock → order → redirect | duplicate submit, expired order | clear refusal or order state |
| Payment 付款 | confirmation → paid | callback → verify / re-query → settlement | missing / forged / late callback | order warning + reconciliation |
| Refund 退款 | request → status | provider request → pending → reconcile | provider timeout, partial refund | refund exception on the order |
| Shipping 物流 | fulfilment → delivered | parcel → carrier event → notice | duplicate / out-of-order event | traceable shipment issue |
| Invoice 發票 | order → invoice | paid order → obligation → book / correction | failed or missing obligation | visible invoice finding |
| Download 下載 | paid → download | entitlement → pinned file key | expired link, file replaced | recoverable access |
Seven questions for every connection｜每一條串接問七個問題: is it actually called? is the result saved? safe if retried twice? one authoritative state when systems disagree? can a job stop unnoticed? does an unresolved case show on the order page, not only in logs? is there a test that breaks this connection?
This is the beginning of the README. Read the rest at the original. Read the full README ↗
