What problem does it solve? Verifying Batch API changes requires coordinating colocated unit tests, a live local Tilt stack with emulators, vitest e2e suites, and a test-quality audit — this Skill consolidates that entire verification workflow into one repeatable process. ## Core Features & Use Cases - Unit test authoring: Colocated bun:test suites for contracts, adapters, and skins driven by committed fixtures, golden vectors, and sync-parity assertions. - Live local stack driving: Launch and readiness-check the Tilt stack (fake provider, Spanner/Pub/Sub emulators, Redis rate limiter), submit batches through real ingress, and capture persisted-row evidence. - E2E and audit coverage: Run the vitest happy path in tests/e2e/api/batches, enforce intent-test traceability for new providers, and audit test quality before hand-off. - Use Case: After adding a new batch provider adapter, use this Skill to write parity tests, drive a live submit through the local stack, run the e2e suite one file at a time, and produce the audit report. ## Quick Start Ask the agent to write and run the Batch API tests for your change, driving the local Tilt stack and capturing persisted-row evidence.
