stripe-catalogue-sync

Sync Stripe products and prices from a bundle catalogue in test and live modes.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill stripe-catalogue-sync-diy-accounting-uk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe-catalogue-sync
Source: https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk/tree/main/.claude/skills/stripe-catalogue-sync
Command: npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill stripe-catalogue-sync-diy-accounting-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping Stripe products and prices in sync with a bundle catalogue is error-prone when done by hand, especially across test and live modes. This Skill runs the repository's stripe-setup script safely: dry run first, test mode on approval, live mode on a separate explicit approval, then lands the resulting price ids in the environment files. ## Core Features & Use Cases - Dry-run planning: Lists which Stripe products and prices already exist and which would be created, writing nothing, so the operator can review the plan first. - Staged test and live sync: Runs the sync in Stripe test mode on one approval, then requires a separate explicit approval before touching live mode. - Price id landing: Writes the printed STRIPE_PRICE_ID_* and STRIPE_TEST_PRICE_ID_* values into .env.ci and .env.prod and opens a PR with only those changes. - Use Case: A bundle's subscription price changes in web/public/submit.catalogue.toml. Invoke this Skill to dry-run the change, create the new price in test and live Stripe, and commit the new price ids without ever exposing secret keys. ## Quick Start Ask the assistant to sync the Stripe catalogue for the bundle whose price just changed, starting with a dry run in test mode.

Frequently Asked Questions about stripe-catalogue-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Stripe products and prices from a catalogue file?▼

Run the stripe-setup script, which reads the catalogue TOML and creates or finds a matching Stripe product and price for each bundle carrying an amount, currency, and interval. Start with --dry-run to review the plan before any writes.

How do I update a Stripe price when a subscription bundle price changes?▼

Update the catalogue values, then run the sync script. It finds the product by metadata.bundleId and creates a new price matching the new amount, leaving the old price active so existing subscriptions keep billing until migrated.

Can I test Stripe product creation before going live?▼

Yes. Run the script with the Stripe test secret key first, using --dry-run to preview and then without it to create test-mode objects. Live mode requires a separate explicit approval and its own dry run.

How do I avoid leaking Stripe secret keys in shell history?▼

Fetch the key inline from AWS Secrets Manager into a single command's environment, so it never lands in history files or logs. Only the printed price ids are captured and committed; keys are never printed or committed.

What happens to existing subscribers when a new Stripe price is created?▼

Existing subscriptions keep billing at the old price because the old price stays active. Only new checkouts use the new price id, and migrating existing subscribers is a separate operator decision.