Catch the tracking call your agent’s diff broke, before the pull request opens.
Your agent writes the diff, then decides the diff is complete. Both halves come out of the same model in the same pass, with the same blind spots, so the check that catches a dropped tracking call has to come from outside it.
No card needed, minutes to connect.
4 finding classes checked against your planned baseline, deterministically, every run.
Agent
Complete. The feature works and the tests pass.
Check
signup_completed is no longer recorded on this path.
The claim does not improve as the models do
The feature ships, the tests pass, an event stopped firing three commits ago.
Skene runs as a hosted MCP server
MCP is the protocol your agent uses to call outside tools. Your agent calls the check in the same session, before it opens the pull request.
The two paths can disagree
One is a deterministic comparison, the other a model judging the diff.
An agent checking its own tracking is checking its own work.
Agent
Complete. The feature works and the tests pass.
Check
signup_completed is no longer recorded on this path.
Your agent calls the diff complete.
A check that did not write it says signup_completed is no longer recorded on this path.
Compares your diff against a baseline the agent never touches.
The check loads the planned event baseline from your workspace journey artifacts, preferring the latest journey.yaml snapshot, and compares it against the events a scan found in the code.
- An event the journey plans for that no longer fires
- A database event whose table is not there
- A tracking call for an event nobody planned
- A planned property the call stopped sending
- Missing event
- fails gate
- Missing table
- fails gate
- Unplanned tracking call
- reported
- Dropped property
- reported
A second check that can catch what the first one missed.
Skene Cloud reviews every pull request for removed or broken tracking. It shares no code with the MCP check.
- Too large for a one-click suggestion: a “Prompt to fix this” block
/skene fixrestores removed tracking calls, never adds an event that was never there
No card needed, minutes to connect.
Before you connect it.
The objections a comparator page exists to answer, not the ones it hopes you skip.
Check us before you believe us.
Skene OSS is the MIT-licensed CLI at github.com/SkeneTechnologies/skene. uvx skene analyse-journey . reads the repository and writes the journey to skene-context/journey.yaml. You point it at your own model provider.