Five ways instrumentation breaks. Skene catches them on the PR.
Coding agents are pattern-matchers. They are good at logic and indifferent to side effects. Analytics calls are side effects. These are the failure modes Skene flags.
Removed events
A coding agent refactors a checkout function and the posthog.capture('checkout_completed') call disappears with it. Skene flags the missing call and names the event that used to fire.
Renamed events
An agent helpfully tidies your event names. 'checkout_completed' becomes 'checkoutCompleted', or 'order_placed', or vanishes into a constant. The funnel now splits across two names. Skene flags the rename and shows the old event vs. the new one.
Moved events
A capture call gets moved out of a conditional, into a different code path, or behind a feature flag. It still exists in the code but no longer fires under the same conditions. Skene tracks where in the control flow each event lives.
Altered payloads
A property gets renamed, dropped, or its type silently changes from string to number. Mixpanel keeps accepting it. Your dashboards keep drawing. Funnels break in subtle ways. Skene compares payload shapes call by call.
Conditional firing changes
The if-block guarding the event changes. The event still fires, just not under the same conditions. A retention metric now misses 30% of users. Skene flags conditional changes that affect when an event fires, not just whether the call exists.
The analytics libraries Skene reads
Skene knows the call shape of each library. It tracks the event name, the properties object, and where in the control flow the call sits.
- PostHog
- Mixpanel
- Segment
- Amplitude
- Heap
- Snowplow
Need another library? Open an issue.
Four surfaces, same engine
PR comment
Posted by the GitHub Action. Names the file, the line, and the event affected.
Coding agent feedback
The MCP server returns findings directly to Cursor, Claude Code, or Codex before the agent commits.
JSON output
Hit the cloud validation API from a script or your own automation. Structured findings, no parsing.
Repo audit
Run a one-time snapshot of your current instrumentation surface. Useful before adopting Skene or after a big refactor.
See what your last 10 PRs quietly broke.
Install in a minute. The first repo audit runs in about as long as your CI does.
