Agent skill · software engineering · jeremylongshore
procore-upgrade-migration
Migrate one Procore endpoint contract after a lifecycle, deprecation, version, or webhook payload change using observed traffic and dual-read evidence. Use when the changelog announces a replacement or Integration Health detects deprecated usage. Trigger with: "upgrade a Procore API version", "remove deprecated Procore endpoint", "migrate Procore webhook payload".
Why this skill is useful
Provides specific API call patterns and error handling for Procore's upgrade migration that the AI wouldn't reliably generate on its own.
What it needs
Requires procore account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Procore Endpoint Contract Cutover Overview Migrate the concrete resource and operation named by provider evidence. Procore does not expose one universal pack-wide version transition, so never claim a generic v1-to-v1.1 upgrade without endpoint-specific documentation. Prerequisites Deprecated route, method, version, or payload format and documented replacement API Call Activity Report slice covering every deployed caller Old and new response contracts, test fixtures, rollout owner, and removal deadline Instructions Step 1: Prove affected traffic Find the normalized deprecated route in production activity and search every service, scheduled job, event handler, and shared adapter for callers. Step 2: Diff contracts Compare paths, headers, IDs, query parameters, request fields, response fields, pagination, permissions, status codes, webhook schema, and lifecycle phase. Step 3: Build a compatibility adapter Isolate the new contract behind a resource-specific interface. Normalize only fields the business layer truly needs and preserve provider errors and metadata. Step 4: Verify side by side For reads, compare sanitized result sets and state hashes. For writes, use sandbox fixtures or a provider-supported idempotent strategy; do not duplicate live mutations. Step 5: Roll out by cohort Canary the new adapter, monitor error and rate signals, and keep an explicit rollback boundary while the old route remains supported. Step 6: Remove the old path After traffic evidence reaches zero and the observation clears, remove compatibility code, fixtures, configuration, and documentation for the deprecated contract. Authentication Both contracts use the intended OAuth 2.0 principal and company boundary. A migration must not widen DMSA permissions or switch grant types unless that separate security change is reviewed. Tool Discipline Use Read and Grep to inspect changelogs, activity reports, adapters, and callers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-upgrade-migration--baa473