Agent skill · posthog
extending-hobby-smoke-tests
Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data but cannot query it.
What it needs
About 4k tokens when loaded.
What this skill does
Extending Hobby smoke tests Treat Hobby CI as proof that a supported Hobby install works across real process boundaries. Keep each check small, strong, and limited to a stable product surface. Decide whether the check belongs Add a check only when all of these are true: The product is supported for Hobby deployments and is no longer alpha. A break can leave the install apparently healthy while the product is unusable. The check crosses boundaries that unit or service integration tests cannot cover, such as capture, queue, consumer, storage, and query API. The released Hobby images and default compose topology contain every required service. A deterministic request and an exact read-back assertion are available. Do not add the check when it requires a private feature flag, a CI-only service topology, or a different image registry only to make an alpha path available. Test that path at a lower layer until it becomes part of the supported Hobby install. If the check exposes a missing service or configuration that every supported Hobby install needs, fix the install and add the check together. If the missing plumbing exists only for the proposed test, stop and reconsider the check. Map the round trip before editing Write down this chain from repository evidence: Verify each link: 1. Find an existing end-to-end or receiver fixture for the ingest payload. Reuse its envelope and minimum valid data instead of inventing a plausible payload. 2. Locate the consumer command and confirm it exists in the released image used by docker-compose.hobby.yml. 3. Confirm the consumer is already started by the default Hobby compose files. 4. Confirm no unreleased or private feature flag is required. 5. Find the supported read API and its personal API-key scope. 6. Identify a unique value that can select only the captured object. Do this before starting a full Hobby run. A successful HTTP capture response proves receipt, not ingestion. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/extending-hobby-smoke-tests