Agent skill · software engineering · jeremylongshore
procore-ci-integration
Gate Procore adapters in CI with offline contract fixtures, host and secret guards, pagination tests, retry safety, and optional bounded sandbox checks. Use when adding endpoints or preventing integration regressions. Trigger with: "test Procore in CI", "add Procore contract tests", "gate a Procore adapter".
Why this skill is useful
Provides specific implementation patterns and API call examples for Procore's REST API 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 Adapter CI Contract Overview Make offline fixtures the default CI denominator and isolate credentialed sandbox tests behind explicit protection. The gate should detect endpoint drift, first-page-only bugs, unsafe retries, tenant-routing loss, and secret leakage without mutating production. Prerequisites Resource adapter inventory and current public endpoint references Sanitized success and failure fixtures with provenance Protected sandbox credential source and cleanup owner for optional live tests Instructions Step 1: Define contract cases Cover required headers, request and response shapes, API version, pagination links, 401, 403, hidden 404, 422, 429, 503, and timeout behavior for each changed adapter. Step 2: Add safety guards Fail if a test selects production hosts, lacks explicit company context where required, prints Authorization data, or enables provider mutations outside a protected sandbox job. Step 3: Test pagination and retries Verify Link navigation reaches every fixture page and stops without next. Assert reset and retry headers control timing and writes are not replayed without reconciliation. Step 4: Validate fixtures Grep for secret patterns, customer identifiers, time-sensitive assertions, and undocumented routes. Require reviewed provenance when a fixture changes. Step 5: Run bounded provider checks Use a Developer Sandbox only when protected credentials are present. Create uniquely prefixed test data, record IDs, and clean it up; otherwise report the provider lane as skipped. Step 6: Emit a gate receipt Record release identifier, adapter set, fixture hashes, offline results, provider-lane status, cleanup result, and known gaps. Authentication Offline tests use synthetic tokens only. Optional provider checks obtain a sandbox OAuth 2.0 Bearer token from protected CI secrets, never expose it, and categorically reject production credentials and hosts. Tool Discipline Use Read and Grep to inspect adapters, fixtures, workflows, and logs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-ci-integration