Agent skill · software engineering · jeremylongshore
ramp-upgrade-migration
Upgrade a Ramp integration across API, schema, scope, endpoint, or behavior changes using impact analysis, dual verification, and reversible rollout. Use when addressing changelog items, deprecated endpoints, or regenerated clients. Trigger with "upgrade Ramp API" or "Ramp breaking change".
Why this skill is useful
Provides specific API integration patterns and error handling for Ramp's corporate card management that the AI wouldn't reliably generate on its own.
What it needs
Requires ramp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ramp API Contract Upgrade Overview Treat documentation or schema drift as a migration. Diff the exact contracts, map affected business behavior and stored data, then canary a reviewed artifact without silently changing scopes or writes. Prerequisites Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary. Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation. Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved. Prepare approved secret storage and a sanitized evidence location. Current Contract Ramp publishes a changelog, OpenAPI schema, guide exports, and API reference; each may reveal a different class of impact. Legacy Cards endpoints are being deprecated for virtual-card management in favor of Funds and Cards (Virtual). Adding configured scopes does not update an existing token; new tokens are required. Unknown fields may be accepted or rejected by endpoint, so compatibility must be tested against the current schema. Authentication Preserve the approved OAuth grant and minimum scopes while comparing contracts. If required scopes change, configure them through review, issue a new environment-bound bearer token, revoke superseded credentials, and repeat positive and negative authority tests. Instructions 1. Freeze old and new OpenAPI checksums, relevant guide/changelog snapshots, client version, endpoint manifest, scopes, stored schemas, and exact deployed artifact. 2. Diff paths, verbs, request/response fields, enums, requiredness, pagination, money units, errors, limits, deprecations, and authorization. 3. Classify each consumer and stored record as compatible, adapter-needed, backfill-needed, behavior-changed, scope-changed, or blocked. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-upgrade-migration