Agent skill · software engineering · jeremylongshore
bamboohr-local-dev-loop
Create a fast BambooHR development loop with synthetic fixtures, a recording- free fake transport, contract tests, and opt-in test-tenant reads. Use when developing safely without copying employee data onto laptops. Trigger with "BambooHR local dev", "mock BambooHR", or "BambooHR test fixtures".
Why this skill is useful
Adds a complete local development setup with hot reload, mocking, and testing scripts specifically for BambooHR API integrations.
What it needs
Requires node 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 Local Development Loop Overview Make local iteration independent of production HR data and network availability. Use a fake transport whose fixtures are designed from the official schema, not recorded from real employees. 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 The official OpenAPI and SDK docs define operations, status codes, auth modes, pagination, and typed errors. They are suitable inputs for contract fixtures; they do not authorize copying actual BambooHR payloads into a repository. Authentication Default local configuration uses obvious non-secret placeholders and a fake transport. A live test-tenant profile is separate, ignored by version control, loaded from an approved secret store, and never activated by ordinary test or watch commands. Instructions 1. Inspect runtime, package manager, test framework, local configuration, and current BambooHR adapter. 2. Put a transport interface behind the adapter. Implement an in-memory fake with explicit scripted responses and request assertions. 3. Create synthetic employees and HR objects with impossible domains and values. Cover active/inactive/future states, missing permitted fields, pagination, empty results, and schema drift without realistic government IDs or records. 4. Add scenarios for 401, 403, 409, 412, 413, 422, 429, 503, 504, 598, timeout, redaction, request IDs, and ambiguous mutation outcome. 5. Add a watch command that runs offline unit/contract tests only. Keep any integration test behind an explicit profile and approval gate. 6. For webhook development, generate payloads locally, verify raw-byte HMAC behavior with a synthetic key, and test replay/idempotency. Do not capture a real delivery as a fixture. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-local-dev-loop