Add ingestion-warnings skill#207
Draft
luke-belton wants to merge 2 commits into
Draft
Conversation
A stepwise context-mill skill that diagnoses and fixes the instrumentation behind a project's ingestion warnings. It queries `system.ingestion_warnings` to see which warning types are actually firing (with a code-scan fallback when the data can't be read), traces each one back to the producing code, applies the smallest fix, and writes a report. Covers illegal / already-identified merges, invalid UUIDs and timestamps, future-dated events, the 1MB size limit, ingestion overflow, invalid replay timestamps, $set on exception events, and invalid heatmap data (relative $current_url). The `cli:` block registers it as `wizard ingestion-warnings`. Generated-By: PostHog Code Task-Id: 9e7dceff-bc33-4dcd-bf3d-aa14f0abee65
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
Generated-By: PostHog Code Task-Id: 9e7dceff-bc33-4dcd-bf3d-aa14f0abee65
This was referenced Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new stepwise context-mill skill,
ingestion-warnings, that diagnoses and fixes the instrumentation behind a PostHog project's ingestion warnings — events PostHog had to drop, mis-merge, or degrade on the way in.The skill is data-first:
system.ingestion_warningsover the last 7 days to see which warning types are actually firing, with example payloads. Falls back to a code scan of all known anti-patterns if the data can't be read.$seton exception events, and invalid heatmap data from a relative$current_url). Each entry has a locate-grep and a minimal fix; it only touches code tied to a firing warning.posthog-ingestion-warnings-report.md(fixed / partial / needs-manual / not-found).The
cli:block registers it aswizard ingestion-warnings, so the command ships with a context-mill release. A companion wizard PR adds a first-class program (custom messaging + abort cases) on top of the generic agent-skill path.Why
Ingestion warnings always trace back to an SDK misuse with a known fix, but today they surface as a generic health issue with no remediation path. This encodes the catalog once so an agent can fix the producing code directly. Raised in a Slack thread off the back of the recurring
invalid_heatmap_data/ relative-$current_urlreports.Testing
node scripts/build.js— skill assembles; chain links + preamble inject correctly (non-terminal steps get the "Read ONLY this file" preamble + continuation link; terminal step gets neither);skill-menu.jsongets theingestion-warningscommand entry.pnpm test:skills— green (70 tests).node scripts/scan-warlock.js dist/skills— passed, no threats.Created with PostHog from a Slack thread