Agent skill · software engineering · jeremylongshore
ramp-ci-integration
Build deterministic CI gates for a Ramp integration using the official OpenAPI contract, local fixtures, and explicitly approved sandbox probes. Use when adding pull-request checks, schema drift detection, or release evidence. Trigger with "Ramp CI" or "test Ramp integration".
Why this skill is useful
Provides specific API call 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 Sandbox Contract Tests and CI Gates Overview Separate fast deterministic contract checks from credentialed sandbox smoke tests. CI should reject schema drift and unsafe production targeting without making financial writes or depending on mutable live data. 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 canonical OpenAPI document for the Developer API and machine-readable guide exports for current behavior. The sandbox is isolated from production and cannot move real money; its current API host is https://demo-api.ramp.com. Credentialed checks still require the minimum OAuth scopes, and production credentials do not belong in pull-request jobs. Unknown fields may be ignored by some endpoints and rejected by others, so request fixtures must be validated against the exact endpoint schema. Instructions 1. Pin a reviewed copy or checksum of the official OpenAPI document and generate schema fixtures from only the endpoints the integration uses. 2. Run unit tests with sanitized success, validation, authorization, rate-limit, timeout, and pagination fixtures; assert secret redaction and idempotency behavior. 3. Add a drift job that compares the pinned contract with the current official document and produces a human-reviewed change report instead of silently regenerating clients. 4. Gate credentialed sandbox smoke tests behind trusted branches and protected secrets; prove the resolved host is demo-api.ramp.com before any request. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-ci-integration--8f907b