Đang tải…
Đang tải…
Spend and activity report for agent-driven DoorDash ordering - reconciles the audit log against real order history and renders totals, per-restaurant breakdown, repeat rate, and abandoned-cart rate
npx claude-code-templates@latest --command doordash/doordash-reportReport period: $ARGUMENTS (default: week)
Data sources: ~/.claude/dd-guard/audit.jsonl (written by the doordash-audit-log
hook), ~/.claude/dd-guard/ledger.jsonl (if doordash-spend-guard is installed),
and live dd-cli order history.
wc -l < ~/.claude/dd-guard/audit.jsonl 2>/dev/null || echo "0"cat ~/.claude/dd-guard/last-reconciled 2>/dev/null || echo "(never)"dd-cli order history and parse the entries (date, restaurant,
total, order_uuid).
checkout_url audit events (and ledger intents) against history
entries by date proximity and cart/order uuid where visible:
~/.claude/dd-guard/last-reconciled with today's date. If
doordash-spend-guard's ledger exists, flip matched intents to paid /
abandoned exactly as /doordash-budget reconcile would.DoorDash activity — week of 2026-07-13
Confirmed spend: $87.40 (prev week $52.10, +68%)
Orders: 4 confirmed, 1 abandoned cart (20% abandon rate)
By restaurant: Sweetgreen $34.90 (2x) · Thai Palace $28.50 · ...
Repeat rate: 75% of orders were reorders/playbooks
Agent activity: 12 searches, 9 cart mutations, 5 checkout URLs
month argument widens the window to 30 days and adds a week-by-week
spend line.For questions like "what did I order most?" or "how much on ramen this
month?", query the audit log with jq (the doordash-order-ledger skill documents
recipes) — never answer from memory.
cuisine-map.json (restaurant → cuisine) next to the audit log if
the user wants cuisine grouping; persist their corrections there.~/.claude/dd-guard/ out of any repo.