Agent skill · software engineering · jeremylongshore
bamboohr-ci-integration
Build CI gates for a BambooHR connector using current OpenAPI contracts, synthetic HR fixtures, secret scanning, and an opt-in tenant smoke test. Use when adding regression coverage or blocking unsafe releases. Trigger with "BambooHR CI", "BambooHR contract tests", or "test BambooHR integration".
Why this skill is useful
Adds a complete CI/CD pipeline configuration with GitHub Actions for BambooHR, including secret management and testing scripts that are not commonly found in public documentation.
What it needs
Requires gh, npm installed locally. Requires bamboohr account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
BambooHR CI Contract Overview Create a fail-closed test lane that proves request construction, schema handling, redaction, retries, and tenant isolation without placing production BambooHR credentials or employee records in routine CI. Prerequisites The target repository or integration path and the requested operator outcome. The tenant, identity, and data scope only when approved live work is in scope. The current evidence register plus customer-specific permissions and agreements. Current Contract Use the pinned OpenAPI from BambooHR's official SDK repository as the endpoint and schema authority. Record the upstream commit and review diffs before updating the pin. Dataset v1 and legacy report deprecations must be regression assertions, not silently normalized away. Authentication Unit and contract tests use synthetic credentials that can never authenticate. An optional live smoke job uses a dedicated least-privilege identity in an approved test tenant, is disabled for forks, and never exposes secrets to pull- request code or artifacts. Instructions 1. Inspect the repository's runtime, test framework, CI provider, generated-code policy, and secret-scanning rules. 2. Add synthetic unit tests for tenant validation, auth header creation, token-refresh persistence, redaction, error typing, retry boundaries, and idempotency decisions. 3. Pin BambooHR's official OpenAPI commit and add contract tests for only the operations the application uses. Alert on removed operations, auth changes, changed required fields, response/status drift, or new deprecations. 4. Use invented names and values in fixtures. Include adversarial cases for cross-tenant IDs, permission-denied fields, oversized pages, webhook replay, malformed signatures, and PII-like strings that must be redacted. 5. Make formatting, static analysis, tests, contract diff, secret scan, and artifact scan required. Upload only reports proven free of payload data. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-ci-integration