stripe-knowledge-patch

Reconcile Stripe API changes across Node.js and Python versions.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill stripe-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/stripe-knowledge-patch/skills/stripe-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill stripe-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Stripe Knowledge Patch provides up-to-date guidance on Stripe API changes since the training cutoff, helping engineers keep integrations compatible across versions.

Core Features & Use Cases

  • Tracks API-version changes and breaking changes (Acacia to Dahlia).
  • Covers key areas: Decimal fields in stripe-node v21, dict removal in stripe-python v15, Billing Mode, Accounts v2, Event Destinations, and related references.
  • Use Case: When upgrading a Stripe integration, consult this patch to update code, tests, and docs to align with the latest API behavior.

Quick Start

Review the patch guidance and update your codebase to align with the latest Stripe API changes.

Frequently Asked Questions about stripe-knowledge-patch

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

FAQPage Schema
How do I handle breaking Stripe API changes when upgrading my integration?

To handle Stripe API changes during an upgrade, identify and reconcile version differences from Acacia through Dahlia. This process updates your code, tests, and references to prevent integration failures using provided guidance.

What Stripe API version changes do I need to track for stripe-node v21?

For stripe-node v21, track the transition to decimal fields. Reconciling these specific API changes ensures your Node.js integration aligns with the latest API behavior and prevents version-related breaks.

How do I fix the dict removal breaking change in stripe-python v15?

To fix the dict removal in stripe-python v15, apply targeted code updates based on API change reconciliation guidance. This updates your Python integration to match new structural requirements and maintains compatibility.

Does the Stripe API patch cover Accounts v2 and Billing Mode migrations?

Yes, the Stripe API patch covers Accounts v2, Billing Mode, and Event Destinations. It enforces guidance on code updates and new field usage to ensure seamless version migration across your integration.

When should I reconcile Stripe API changes to prevent integration breaks?

Reconcile Stripe API changes when upgrading your integration across versions, specifically from Acacia to Dahlia. Consulting patch guidance beforehand prevents breaking changes in Node.js and Python clients.