Setup, the PR check, and the fix.
No SDK to swap, no data pipeline to wire up. Skene reads the event-writing code and the Supabase schema you already have, and runs as a GitHub Action on every pull request.
Setup
Connect the repository and your Supabase project, read-only. Skene scans the code for every write that records an event and reads the schema for the tables those events are meant to land in. That pair, the events and the tables they map to, becomes the baseline.
The PR check
Add the GitHub Action. On every pull request, Skene re-reads the changed files, compares them against the baseline, and checks that each event still fires and still matches the table it belongs to. A removed write, a renamed column, or a payload the schema cannot store shows up as a comment on the PR, naming the event, the file, and what stops being recorded.
The fix
When Skene finds a break, it proposes the corrected write as a commit on the same PR. You review and merge, or mark the change intentional and the baseline updates. Merging past an unresolved break fails the check.
After merge, Skene keeps checking on a schedule, so drift that lands through a path the PR gate did not cover still surfaces. The baseline tracks the codebase as it grows. That verified record of every event is also what your coding agent queries over MCP, for the paths and cohorts that drive revenue.
Patch the code tomorrow. The data from this week is already gone.
A renamed event passes every test, ships green, and sits broken for weeks before anyone notices. Skene runs as a GitHub Action on every pull request, reads your Supabase schema read-only, and comments the moment a write breaks, while your data is still recoverable. Usage-based on tokens, with $5 of free cloud credit to start. A PR that touches none of your tracking costs nothing.
